Re: [PATCH v2] ipv6: addrconf: Fix recursive spin lock call

On Tue, 2016-02-02 at 02:11 +0000, subashab@codeaurora.org wrote:

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 -

Acked-by: Eric Dumazet <edumazet@google.com>