[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a8ed41f3-1576-cbf6-907a-f501b3df189e@gmail.com>
Date: Wed, 17 Apr 2019 19:02:11 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: linmiaohe <linmiaohe@...wei.com>,
Eric Dumazet <eric.dumazet@...il.com>, wensong@...ux-vs.org,
horms@...ge.net.au, ja@....bg, pablo@...filter.org,
kadlec@...ckhole.kfki.hu, fw@...len.de, davem@...emloft.net,
netdev@...r.kernel.org, lvs-devel@...r.kernel.org,
netfilter-devel@...r.kernel.org, coreteam@...filter.org,
linux-kernel@...r.kernel.org
Cc: Mingfangsen <mingfangsen@...wei.com>, liujie165@...wei.com
Subject: Re: [PATCH] ipvs:set sock send/receive buffer correctly
On 04/17/2019 06:45 PM, linmiaohe wrote:
>
> In fact, I just implemented this function with reference to
> sock_setsockopt(). When val * 2 overflow, we will set the
> buffer as SOCK_MIN_SNDBUF, just as sock_setsockopt() do.
>
I do not think so.
Please check latest linux kernel, not some old version.
commit 4057765f2dee79cb92f9067909477303360be8d3 sock: consistent handling of extreme SO_SNDBUF/SO_RCVBUF values
Powered by blists - more mailing lists