From 287776ddf47ec931880863a64e8d5094cb2b2dfa Mon Sep 17 00:00:00 2001 From: Daichi Hirono Date: Fri, 28 Apr 2017 16:55:29 +0900 Subject: [PATCH] Use SO_SNDBUFFORCE instead of SO_SNDBUF When /proc/sys/net/core/wmem_max is smaller than kMaxMessageSize, we need to override the limitation. Bug: 37561460 Test: libappfuse_tests Change-Id: Ibaac8db61290d661459fdc46f0ae8416f7db1d9e --- libappfuse/FuseBuffer.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libappfuse/FuseBuffer.cc b/libappfuse/FuseBuffer.cc index b42a04954..fd69849a7 100644 --- a/libappfuse/FuseBuffer.cc +++ b/libappfuse/FuseBuffer.cc @@ -141,8 +141,8 @@ bool SetupMessageSockets(base::unique_fd (*result)[2]) { } constexpr int kMaxMessageSize = sizeof(FuseBuffer); - if (setsockopt(fds[0], SOL_SOCKET, SO_SNDBUF, &kMaxMessageSize, sizeof(int)) != 0 || - setsockopt(fds[1], SOL_SOCKET, SO_SNDBUF, &kMaxMessageSize, sizeof(int)) != 0) { + if (setsockopt(fds[0], SOL_SOCKET, SO_SNDBUFFORCE, &kMaxMessageSize, sizeof(int)) != 0 || + setsockopt(fds[1], SOL_SOCKET, SO_SNDBUFFORCE, &kMaxMessageSize, sizeof(int)) != 0) { PLOG(ERROR) << "Failed to update buffer size for socket"; return false; }