public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Mike Manning <mmanning@brocade.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] net: ipv6: Remove addresses for failures with strict DAD
Date: Wed, 17 Aug 2016 18:16:06 +0200	[thread overview]
Message-ID: <1471450566.1738924.698156465.68BB29E2@webmail.messagingengine.com> (raw)
In-Reply-To: <ae4a3e5a-1b36-5eab-da03-d6121abb6223@brocade.com>

On Wed, Aug 17, 2016, at 18:08, Mike Manning wrote:
> On 08/17/2016 04:40 PM, Hannes Frederic Sowa wrote:
> > On 17.08.2016 12:28, Mike Manning wrote:
> >> +static void dev_disable_change(struct inet6_dev *idev);
> >>  
> >>  /*
> >>   *	Configured unicast address hash table
> >> @@ -1945,6 +1946,12 @@ lock_errdad:
> >>  
> >>  			pr_info("%s: IPv6 being disabled!\n",
> >>  				ifp->idev->dev->name);
> >> +			spin_unlock_bh(&ifp->lock);
> >> +			addrconf_dad_stop(ifp, 1);
> >> +			rtnl_lock();
> >> +			dev_disable_change(idev);
> >> +			rtnl_unlock();
> >> +			return;
> >>  		}
> >>  	}
> > 
> > You can't take rtnl_lock at that point but must postpone the actions and
> > do that in addrconf_dad_work.
> > 
> > Probably the whole ... else if (idev->cnf.accept_dad > 1 && ...) needs
> > to move there.
> > 
> > Bye,
> > Hannes
> > 
> > 
> 
> Thanks for the prompt review, I will look into making these changes.
> 
> Also these changes caused a build error due to conditional compilation
> without CONFIG_SYSCTL, which is resolved by replacing the call to
> dev_disable_change(idev) by directly calling addrconf_ifdown(idev->dev,
> 0) instead.
> 
> I would appreciate any further comments if the suggested change in
> behavior is not acceptable.

What you describe in the changelog what is happening right now looks
like a bug to me thus your patch made sense to me.

Bye,
Hannes

      reply	other threads:[~2016-08-17 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17 10:28 [PATCH] net: ipv6: Remove addresses for failures with strict DAD Mike Manning
2016-08-17 14:01 ` kbuild test robot
2016-08-17 15:07 ` kbuild test robot
2016-08-17 15:40 ` Hannes Frederic Sowa
2016-08-17 16:08   ` Mike Manning
2016-08-17 16:16     ` Hannes Frederic Sowa [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=1471450566.1738924.698156465.68BB29E2@webmail.messagingengine.com \
    --to=hannes@stressinduktion.org \
    --cc=mmanning@brocade.com \
    --cc=netdev@vger.kernel.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