Patch "ipv6: addrconf: Fix recursive spin lock call" has been added to the 4.4-stable tree
Subsystems (3)
This is a note to let you know that I've just added the patch titled
ipv6: addrconf: Fix recursive spin lock call
to the 4.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
ipv6-addrconf-fix-recursive-spin-lock-call.patch
and it can be found in the queue-4.4 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From foo@baz Mon Feb 29 14:33:50 PST 2016
From: "[email protected]" <[email protected]>
Date: Tue, 2 Feb 2016 02:11:10 +0000
Subject: ipv6: addrconf: Fix recursive spin lock call
From: "[email protected]" <[email protected]>
[ Upstream commit 16186a82de1fdd868255448274e64ae2616e2640 ]
A rcu stall with the following backtrace was seen on a system with forwarding, optimistic_dad and use_optimistic set. To reproduce, set these flags and allow ipv6 autoconf.
This occurs because the device write_lock is acquired while already holding the read_lock. Back trace below -
INFO: rcu_preempt self-detected stall on CPU { 1} (t=2100 jiffies
g=3992 c=3991 q=4471)<6> Task dump for CPU 1:
<2> kworker/1:0 R running task 12168 15 2 0x00000002
<2> Workqueue: ipv6_addrconf addrconf_dad_work <6> Call trace:
<2> [<ffffffc000084da8>] el1_irq+0x68/0xdc
<2> [<ffffffc000cc4e0c>] _raw_write_lock_bh+0x20/0x30 <2> [<ffffffc000bc5dd8>] __ipv6_dev_ac_inc+0x64/0x1b4 <2> [<ffffffc000bcbd2c>] addrconf_join_anycast+0x9c/0xc4 <2> [<ffffffc000bcf9f0>] __ipv6_ifa_notify+0x160/0x29c <2> [<ffffffc000bcfb7c>] ipv6_ifa_notify+0x50/0x70 <2> [<ffffffc000bd035c>] addrconf_dad_work+0x314/0x334 <2> [<ffffffc0000b64c8>] process_one_work+0x244/0x3fc <2> [<ffffffc0000b7324>] worker_thread+0x2f8/0x418 <2> [<ffffffc0000bb40c>] kthread+0xe0/0xec
v2: do addrconf_dad_kick inside read lock and then acquire write lock for ipv6_ifa_notify as suggested by Eric
addresses useful candidates")
--- net/ipv6/addrconf.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
net/ipv6/addrconf.c +4 -1
@@ -3506,6 +3506,7 @@ static void addrconf_dad_begin(struct in {struct inet6_dev *idev = ifp->idev;struct net_device *dev = idev->dev; +bool notify = false;addrconf_join_solict (dev, &ifp->addr);
@@ -3551,7 +3552,7 @@ static void addrconf_dad_begin(struct in/* Because optimistic nodes can use this address, * notify listeners. If DAD fails, RTM_DELADDR is sent. */ -ipv6_ifa_notify (RTM_NEWADDR , ifp); + notify = true; } }
@@ -3559,6 +3560,8 @@ static void addrconf_dad_begin(struct in out:spin_unlock (&ifp->lock);read_unlock_bh (&idev->lock); +if (notify) +ipv6_ifa_notify (RTM_NEWADDR , ifp); }static void addrconf_dad_start (struct inet6_ifaddr *ifp)
Patches currently in stable-queue which might be from [email protected] are
queue-4.4/ipv6-addrconf-fix-recursive-spin-lock-call.patch