From: David Miller <davem@davemloft.net>
To: okir@lst.de
Cc: netdev@vger.kernel.org
Subject: Re: Races in net_rx_action vs netpoll?
Date: Mon, 09 Jul 2007 15:27:46 -0700 (PDT) [thread overview]
Message-ID: <20070709.152746.75758774.davem@davemloft.net> (raw)
In-Reply-To: <200707041416.33732.okir@lst.de>
From: Olaf Kirch <okir@lst.de>
Date: Wed, 4 Jul 2007 14:16:32 +0200
Another locking bug in netpoll, why am I not surprised? :-/
Thanks for reporting this Olaf.
> I think the only real fix for this is to restrict who is allowed
> to remove the interface from the poll_list. Only net_rx_action
> should be allowed to do so. A possible patch is given below
> (beware, it's untested so far)
I'm happy to entertain this kind of solution, but we really
need to first have an interface to change multiple bits
at a time in one atomic operation, because by itself this
patch doubles the number of atomices we do when starting
a NAPI poll.
> static inline int __netif_rx_schedule_prep(struct net_device *dev)
> {
> + /* The driver may have decided that there's no more work
> + * to be done - but now another interrupt arrives, and
> + * we changed our mind. */
> + smp_mb__before_clear_bit();
> + clear_bit(__LINK_STATE_RX_COMPLETE, &dev->state);
> +
> return !test_and_set_bit(__LINK_STATE_RX_SCHED, &dev->state);
> }
>
Because of that change.
next prev parent reply other threads:[~2007-07-10 4:18 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 [this message]
2007-07-10 10:44 ` Olaf Kirch
2007-07-11 5:44 ` David Miller
2007-07-11 7:41 ` Olaf Kirch
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=20070709.152746.75758774.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=okir@lst.de \
/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).