All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: bridge@lists.linux-foundation.org, Neil,
	Cong Wang <amwang@redhat.com>, Horman <nhorman@tuxdriver.com>,
	Jeff, netdev@vger.kernel.org, Andy Gospodarek <gospo@redhat.com>,
	Jay Vosburgh <fubar@us.ibm.com>,
	linux-kernel@vger.kernel.org,
	bonding-devel@lists.sourceforge.net, Moyer <jmoyer@redhat.com>,
	Matt Mackall <mpm@selenic.com>,
	David Miller <davem@davemloft.net>
Subject: Re: [Bridge] [Bonding-devel] [v3 Patch 2/3] bridge: make bridge support netpoll
Date: Mon, 12 Apr 2010 08:38:42 -0700	[thread overview]
Message-ID: <20100412083842.26d71bda@nehalam> (raw)
In-Reply-To: <1271068737.16881.18.camel@edumazet-laptop>

On Mon, 12 Apr 2010 12:38:57 +0200
Eric Dumazet <eric.dumazet@gmail.com> wrote:

> Le lundi 12 avril 2010 à 18:37 +0800, Cong Wang a écrit :
> > Stephen Hemminger wrote:
> > > There is no protection on dev->priv_flags for SMP access.
> > > It would better bit value in dev->state if you are using it as control flag.
> > > 
> > > Then you could use 
> > > 			if (unlikely(test_and_clear_bit(__IN_NETPOLL, &skb->dev->state)))
> > > 				netpoll_send_skb(...)
> > > 
> > > 
> > 
> > Hmm, I think we can't use ->state here, it is not for this kind of purpose,
> > according to its comments.
> > 
> > Also, I find other usages of IFF_XXX flags of ->priv_flags are also using
> > &, | to set or clear the flags. So there must be some other things preventing
> > the race...
> 
> Yes, its RTNL that protects priv_flags changes, hopefully...
> 

The patch was not protecting priv_flags with RTNL.
For example..


@@ -308,7 +312,9 @@ static void netpoll_send_skb(struct netp
 		     tries > 0; --tries) {
 			if (__netif_tx_trylock(txq)) {
 				if (!netif_tx_queue_stopped(txq)) {
+					dev->priv_flags |= IFF_IN_NETPOLL;
 					status = ops->ndo_start_xmit(skb, dev);
+					dev->priv_flags &= ~IFF_IN_NETPOLL;
 					if (status == NETDEV_TX_OK)
 						txq_trans_update(txq);

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Cong Wang <amwang@redhat.com>, Jay Vosburgh <fubar@us.ibm.com>,
	Neil Horman <nhorman@tuxdriver.com>,
	netdev@vger.kernel.org, Matt Mackall <mpm@selenic.com>,
	bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	David Miller <davem@davemloft.net>,
	Jeff Moyer <jmoyer@redhat.com>,
	Andy Gospodarek <gospo@redhat.com>,
	bonding-devel@lists.sourceforge.net
Subject: Re: [Bonding-devel] [v3 Patch 2/3] bridge: make bridge support netpoll
Date: Mon, 12 Apr 2010 08:38:42 -0700	[thread overview]
Message-ID: <20100412083842.26d71bda@nehalam> (raw)
In-Reply-To: <1271068737.16881.18.camel@edumazet-laptop>

On Mon, 12 Apr 2010 12:38:57 +0200
Eric Dumazet <eric.dumazet@gmail.com> wrote:

> Le lundi 12 avril 2010 à 18:37 +0800, Cong Wang a écrit :
> > Stephen Hemminger wrote:
> > > There is no protection on dev->priv_flags for SMP access.
> > > It would better bit value in dev->state if you are using it as control flag.
> > > 
> > > Then you could use 
> > > 			if (unlikely(test_and_clear_bit(__IN_NETPOLL, &skb->dev->state)))
> > > 				netpoll_send_skb(...)
> > > 
> > > 
> > 
> > Hmm, I think we can't use ->state here, it is not for this kind of purpose,
> > according to its comments.
> > 
> > Also, I find other usages of IFF_XXX flags of ->priv_flags are also using
> > &, | to set or clear the flags. So there must be some other things preventing
> > the race...
> 
> Yes, its RTNL that protects priv_flags changes, hopefully...
> 

The patch was not protecting priv_flags with RTNL.
For example..


@@ -308,7 +312,9 @@ static void netpoll_send_skb(struct netp
 		     tries > 0; --tries) {
 			if (__netif_tx_trylock(txq)) {
 				if (!netif_tx_queue_stopped(txq)) {
+					dev->priv_flags |= IFF_IN_NETPOLL;
 					status = ops->ndo_start_xmit(skb, dev);
+					dev->priv_flags &= ~IFF_IN_NETPOLL;
 					if (status == NETDEV_TX_OK)
 						txq_trans_update(txq);

  reply	other threads:[~2010-04-12 15:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  6:18 [Bridge] [v3 Patch 1/3] netpoll: add generic support for bridge and bonding devices Amerigo Wang
2010-04-08  6:18 ` Amerigo Wang
2010-04-08  6:18 ` [Bridge] [v3 Patch 2/3] bridge: make bridge support netpoll Amerigo Wang
2010-04-08  6:18   ` Amerigo Wang
2010-04-08 15:37   ` [Bridge] " Stephen Hemminger
2010-04-08 15:37     ` Stephen Hemminger
2010-04-09  5:43     ` [Bridge] " Cong Wang
2010-04-09  5:43       ` Cong Wang
2010-04-12 10:37     ` [Bridge] " Cong Wang
2010-04-12 10:37       ` Cong Wang
2010-04-12 10:38       ` [Bridge] " Eric Dumazet
2010-04-12 10:38         ` Eric Dumazet
2010-04-12 15:38         ` Stephen Hemminger [this message]
2010-04-12 15:38           ` [Bonding-devel] " Stephen Hemminger
2010-04-13  8:57           ` [Bridge] " Cong Wang
2010-04-13  8:57             ` Cong Wang
2010-04-13 16:52             ` [Bridge] " Jay Vosburgh
2010-04-13 16:52               ` Jay Vosburgh
2010-04-13 17:33               ` [Bridge] " Stephen Hemminger
2010-04-13 17:33                 ` Stephen Hemminger
2010-04-14  8:16                 ` [Bridge] " Cong Wang
2010-04-14  8:16                   ` Cong Wang
2010-04-14  8:11               ` [Bridge] " Cong Wang
2010-04-14  8:11                 ` Cong Wang
2010-04-08  6:19 ` [Bridge] [v3 Patch 3/3] bonding: make bonding " Amerigo Wang
2010-04-08  6:19   ` Amerigo Wang

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=20100412083842.26d71bda@nehalam \
    --to=shemminger@linux-foundation.org \
    --cc=amwang@redhat.com \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=fubar@us.ibm.com \
    --cc=gospo@redhat.com \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.