When running in a container, the process might be in a user/net namespace, which would cause setting the SO_RCVBUFFORCE socket option to fail with EPERM. But rmem_max is set to a high enough value which allows SO_RCVBUF to succeed. Bug: 62417946 Test: Run android in a new user and network namespace, vold does not abort here. Change-Id: I2b678ddd886a406a3394d9fdd33f9c8800ef78a3 Signed-off-by: Junichi Uekawa <uekawa@google.com> (cherry picked from commit b41155d4af0e00fc6f65d7d67b80e7b866f847d6)gugelfrei
parent
da85cb71b3
commit
c865adaa3b
Loading…
Reference in new issue