netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: stephen@networkplumber.org, netdev@vger.kernel.org
Subject: Re: [PATCH v3 net] ipv6: move DAD and addrconf_verify processing to workqueue
Date: Fri, 28 Mar 2014 16:57:03 -0400 (EDT)	[thread overview]
Message-ID: <20140328.165703.1925429348459340241.davem@davemloft.net> (raw)
In-Reply-To: <20140327172807.GB11063@order.stressinduktion.org>

From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Thu, 27 Mar 2014 18:28:07 +0100

> addrconf_join_solict and addrconf_join_anycast may cause actions which
> need rtnl locked, especially on first address creation.
> 
> A new DAD state is introduced which deferres processing of the initial
> DAD processing into a workqueue.
> 
> To get rtnl lock we need to push the code paths which depend on those
> calls up to workqueues, specifically addrconf_verify and the DAD
> processing.
> 
> (v2)
> addrconf_dad_failure needs to be queued up to the workqueue, too. This
> patch introduces a new DAD state and stop the DAD processing in the
> workqueue (this is because of the possible ipv6_del_addr processing
> which removes the solicited multicast address from the device).
> 
> addrconf_verify_lock is removed, too. After the transition it is not
> needed any more.
> 
> As we are not processing in bottom half anymore we need to be a bit more
> careful about disabling bottom half out when we lock spin_locks which are also
> used in bh.
> 
> Relevant backtrace:
 ...
> Hunks and backtrace stolen from a patch by Stephen Hemminger.
> 
> Reported-by: Stephen Hemminger <stephen@networkplumber.org>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
> ---
> v3 (only minor change):
> * reword pr_notice in inet6_ifa_finish_destroy (thanks, David!)

Applied, thanks a lot Hannes.

      reply	other threads:[~2014-03-28 20:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 23:18 [PATCH net] ipv6: fix RTNL assert fail in DAD Stephen Hemminger
2014-03-18  0:29 ` Hannes Frederic Sowa
2014-03-19  0:54   ` Stephen Hemminger
2014-03-19  4:17     ` David Miller
2014-03-19  6:58       ` Stephen Hemminger
2014-03-19 17:53         ` David Miller
2014-03-19 22:44           ` Hannes Frederic Sowa
2014-03-20  3:52             ` David Miller
2014-03-20  6:38               ` Hannes Frederic Sowa
2014-03-23  2:03 ` Hannes Frederic Sowa
2014-03-25  8:03   ` [PATCH net] ipv6: move DAD and addrconf_verify processing to workqueue Hannes Frederic Sowa
2014-03-25 21:20     ` Stephen Hemminger
2014-03-26  0:00       ` Hannes Frederic Sowa
2014-03-26  6:17         ` [PATCH v2 " Hannes Frederic Sowa
2014-03-27 17:15           ` David Miller
2014-03-27 17:28             ` [PATCH v3 " Hannes Frederic Sowa
2014-03-28 20:57               ` David Miller [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140328.165703.1925429348459340241.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=hannes@stressinduktion.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).