From: Olaf Kirch <okir@lst.de>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: Races in net_rx_action vs netpoll?
Date: Wed, 11 Jul 2007 09:41:37 +0200 [thread overview]
Message-ID: <200707110941.38587.okir@lst.de> (raw)
In-Reply-To: <20070710.224457.95896396.davem@davemloft.net>
On Wednesday 11 July 2007 07:44, David Miller wrote:
> > +#ifdef CONFIG_NETPOLL
> > + /* Prevent race with netpoll - yes, this is a kludge.
> > + * But at least it doesn't penalize the non-netpoll
> > + * code path. */
> > + if (test_bit(__LINK_STATE_POLL_LIST_FROZEN, &dev->state))
> > + return;
> > +#endif
> > +
> > local_irq_save(flags);
> > BUG_ON(!test_bit(__LINK_STATE_RX_SCHED, &dev->state));
> > list_del(&dev->poll_list);
>
> That new bit can be set in interrupt context can't it?
It's set and cleared in poll_napi only, and as far as I can tell
poll_napi will only ever be called from via softirq, but never
from an interrupt handler directly.
I also don't think the test_bit() needs to lock out interrupts.
The only reason we do it for the RX_SCHED bit is that the RX_SCHED
bit and the poll_list change must happen atomically wrt interrupts
from the NIC, right?
Olaf
--
Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
okir@lst.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
next prev parent reply other threads:[~2007-07-11 7:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 12:16 Races in net_rx_action vs netpoll? Olaf Kirch
2007-07-09 22:27 ` David Miller
2007-07-10 10:44 ` Olaf Kirch
2007-07-11 5:44 ` David Miller
2007-07-11 7:41 ` Olaf Kirch [this message]
2007-07-12 2:33 ` David Miller
2007-07-19 15:19 ` Olaf Kirch
2007-07-19 16:27 ` Stephen Hemminger
2007-07-22 7:05 ` David Miller
2007-07-24 10:26 ` Jarek Poplawski
2007-07-12 12:59 ` Jarek Poplawski
2007-07-12 13:54 ` Olaf Kirch
2007-07-13 8:55 ` Jarek Poplawski
2007-07-16 8:06 ` Jarek Poplawski
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=200707110941.38587.okir@lst.de \
--to=okir@lst.de \
--cc=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).