From: Cong Wang <amwang@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org,
Sylvain Munaut <s.munaut@whatever-company.com>,
David Miller <davem@davemloft.net>
Subject: Re: Q: what protects dev->napi_list?
Date: Sat, 25 Aug 2012 14:08:42 +0800 [thread overview]
Message-ID: <1345874922.14276.14.camel@cr0> (raw)
In-Reply-To: <1345807778.29722.98.camel@edumazet-glaptop>
On Fri, 2012-08-24 at 13:29 +0200, Eric Dumazet wrote:
> On Fri, 2012-08-24 at 18:39 +0800, Cong Wang wrote:
> >
> > Yeah, but bnx2 driver calls it at other time too, for example
> > bnx2_change_ring_size() which in turn could be called by
> > bnx2_set_channels().
>
> Then at this point, device is stopped, or should be.
>
But poll_napi() is still iterating the dev->napi_list, could anyone
stops it?
IOW, the following race condition may happen:
static void poll_napi(struct net_device *dev)
{
struct napi_struct *napi;
int budget = 16;
WARN_ON_ONCE(!irqs_disabled());
list_for_each_entry(napi, &dev->napi_list, dev_list) {
local_irq_enable();
//<-- Another process may call
//bnx2_change_ring_size() to del
//napi from dev, on other CPU.
local_irq_disable();
}
}
next prev parent reply other threads:[~2012-08-25 6:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 9:46 Q: what protects dev->napi_list? Cong Wang
2012-08-24 10:12 ` Eric Dumazet
2012-08-24 10:39 ` Cong Wang
2012-08-24 11:29 ` Eric Dumazet
2012-08-25 6:08 ` Cong Wang [this message]
2012-08-25 6:49 ` Eric Dumazet
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=1345874922.14276.14.camel@cr0 \
--to=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=s.munaut@whatever-company.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 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).