diff options
author | David S. Miller <davem@davemloft.net> | 2018-03-22 15:12:57 -0400 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-03-22 15:12:57 -0400 |
commit | 1a2e10a24039147047cc21759ec57314c333c1ac (patch) | |
tree | 0b09f0de0ff410fef91ad0224a241b322bd0eb05 /net/bluetooth | |
parent | f2d254fac13cc7c86871ea607c4ab1afa7f13e2e (diff) | |
parent | d9ff3049739e349b5380b96226f9ad766741773d (diff) | |
download | linux-1a2e10a24039147047cc21759ec57314c333c1ac.tar.gz linux-1a2e10a24039147047cc21759ec57314c333c1ac.tar.bz2 linux-1a2e10a24039147047cc21759ec57314c333c1ac.zip |
Merge branch 'Rework-ip_ra_chain-protection'
Kirill Tkhai says:
====================
Rework ip_ra_chain protection
Commit 1215e51edad1 "ipv4: fix a deadlock in ip_ra_control"
made rtnl_lock() be used in raw_close(). This function is called
on every RAW socket destruction, so that rtnl_mutex is taken
every time. This scales very sadly. I observe cleanup_net()
spending a lot of time in rtnl_lock() and raw_close() is one
of the biggest rtnl user (since we have percpu net->ipv4.icmp_sk).
This patchset reworks the locking: reverts the problem commit
and its descendant, and introduces rtnl-independent locking.
This may have a continuation, and someone may work on killing
rtnl_lock() in mrtsock_destruct() in the future.
v3: Change patches order: [2/5] and [3/5].
v2: Fix sparse warning [4/5], as reported by kbuild test robot.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/bluetooth')
0 files changed, 0 insertions, 0 deletions