tree 7da26cb2c9d902798491bfbf9914d21e49758ff8
parent da85cb71b3b49f6d244f1a9727c008271ebb6dc3
author Junichi Uekawa <uekawa@google.com> 1446671154 +0900
committer Luis Hector Chavez <lhchavez@google.com> 1499813514 -0700

Try SO_RCVBUF before SO_RCVBUFFORCE.

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)