netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Julien Grall <julien.grall@citrix.com>,
	xen-devel@lists.xenproject.org, kaber@trash.net,
	kadlec@blackhole.kfki.hu, davem@davemloft.net,
	netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
	bridge@lists.linux-foundation.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Bernhard Thaler <bernhard.thaler@wvnet.at>,
	fw@strlen.de, ian.campbell@citrix.com, wei.liu2@citrix.com,
	Bob Liu <bob.liu@oracle.com>
Subject: Re: [PATCH v2] net/bridge: Use __in6_dev_get rather than in6_dev_get in br_validate_ipv6
Date: Wed, 8 Jul 2015 11:04:21 +0200	[thread overview]
Message-ID: <20150708090421.GA4824@salvia> (raw)
In-Reply-To: <20150707113434.25f77b1e@urahara>

On Tue, Jul 07, 2015 at 11:34:34AM -0700, Stephen Hemminger wrote:
> On Tue, 7 Jul 2015 15:55:21 +0100
> Julien Grall <julien.grall@citrix.com> wrote:
> 
> > The commit efb6de9b4ba0092b2c55f6a52d16294a8a698edd "netfilter: bridge:
> > forward IPv6 fragmented packets" introduced a new function
> > br_validate_ipv6 which take a reference on the inet6 device. Although,
> > the reference is not released at the end.
> > 
> > This will result to the impossibility to destroy any netdevice using
> > ipv6 and bridge.
> > 
> > It's possible to directly retrieve the inet6 device without taking a
> > reference as all netfilter hooks are protected by rcu_read_lock via
> > nf_hook_slow.
> > 
> > Spotted while trying to destroy a Xen guest on the upstream Linux:
> > "unregister_netdevice: waiting for vif1.0 to become free. Usage count = 1"
> > 
> > Signed-off-by: Julien Grall <julien.grall@citrix.com>
> > Cc: Bernhard Thaler <bernhard.thaler@wvnet.at>
> > Cc: Pablo Neira Ayuso <pablo@netfilter.org>
> > Cc: fw@strlen.de
> > Cc: ian.campbell@citrix.com
> > Cc: wei.liu2@citrix.com
> > Cc: Bob Liu <bob.liu@oracle.com>
> > 
> > ---
> >     Note that it's impossible to create new guest after this message.
> >     I'm not sure if it's normal.
> > 
> >     Changes in v2:
> >         - Don't take a reference to inet6.
> >         - This was "net/bridge: Add missing in6_dev_put in
> >         br_validate_ipv6" [0]
> > 
> >     [0] https://lkml.org/lkml/2015/7/3/443
> > ---
> >  net/bridge/br_netfilter_ipv6.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> I like this simple solution
> 
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>

Applied, thanks.

      reply	other threads:[~2015-07-08  8:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 14:55 [PATCH v2] net/bridge: Use __in6_dev_get rather than in6_dev_get in br_validate_ipv6 Julien Grall
2015-07-07 18:34 ` Stephen Hemminger
2015-07-08  9:04   ` Pablo Neira Ayuso [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=20150708090421.GA4824@salvia \
    --to=pablo@netfilter.org \
    --cc=bernhard.thaler@wvnet.at \
    --cc=bob.liu@oracle.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=fw@strlen.de \
    --cc=ian.campbell@citrix.com \
    --cc=julien.grall@citrix.com \
    --cc=kaber@trash.net \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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).