[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20161217.111333.1879745595587471743.davem@davemloft.net>
Date: Sat, 17 Dec 2016 11:13:33 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: tom@...bertland.com
Cc: netdev@...r.kernel.org, kernel-team@...com, jbacik@...com,
eric.dumazet@...il.com, raigatgoog@...il.com
Subject: Re: [PATCH net-next 0/2] inet: Fixes for inet_csk_get_port and
soreusport
From: Tom Herbert <tom@...bertland.com>
Date: Wed, 14 Dec 2016 16:54:14 -0800
> This patch set fixes a couple of issues I noticed while debugging our
> softlockup issue in inet_csk_get_port.
>
> - Don't allow jump into port scan in inet_csk_get_port if function
> was called with non-zero port number (looking up explicit port
> number).
> - When inet_csk_get_port is called with zero port number (ie. perform
> scan) an reuseport is set on the socket, don't match sockets that
> also have reuseport set. The intent from the user should be
> to get a new port number and then explictly bind other
> sockets to that number using soreuseport.
>
> Tested:
>
> Ran first patch on production workload with no ill effect.
>
> For second patch, ran a little listener application and first
> demonstrated that unbound sockets with soreuseport can indeed
> be bound to unrelated soreuseport sockets.
Series applied, thanks Tom.
Powered by blists - more mailing lists