On 06/03/2018 10:47 AM, Maciej Żenczykowski wrote: > From: Maciej Żenczykowski <m...@google.com> > > It is not safe to do so because such sockets are already in the > hash tables and changing these options can result in invalidating > the tb->fastreuse(port) caching. > Reviewed-by: Eric Dumazet <eduma...@google.com>
- [PATCH] net: do not allow changing SO_REUSEADDR/SO_RE... Maciej Żenczykowski
- Re: [PATCH] net: do not allow changing SO_REUSEA... Christoph Paasch
- Re: [PATCH] net: do not allow changing SO_REUSEA... Eric Dumazet
- Re: [PATCH] net: do not allow changing SO_REUSEA... David Miller
- Re: net: do not allow changing SO_REUSEADDR/SO_R... Andrei Vagin
- Re: net: do not allow changing SO_REUSEADDR/... Maciej Żenczykowski
- Re: net: do not allow changing SO_REUSEA... Andrei Vagin
- Re: net: do not allow changing SO_RE... Maciej Żenczykowski
- Re: net: do not allow changing ... Andrei Vagin
- Re: net: do not allow changing SO_REUSEADDR/SO_R... Andrei Vagin
- Re: [PATCH] net: do not allow changing SO_REUSEA... Marc Dionne
- Re: [PATCH] net: do not allow changing SO_RE... Maciej Żenczykowski
- Re: [PATCH] net: do not allow changing S... Marc Dionne