Re: [PATCH net] netfilter: on sockopt() acquire sock lock only in the required scope

On Tue, Jan 30, 2018 at 07:01:40PM +0100, Paolo Abeni wrote:

Syzbot reported several deadlocks in the netfilter area caused by
rtnl lock and socket lock being acquired with a different order on
different code paths, leading to backtraces like the following one:

[...]

The problem, as Florian noted, is that nf_setsockopt() is always
called with the socket held, even if the lock itself is required only
for very tight scopes and only for some operation.

Applied, thanks Paolo.