From: Matt Mackall <mpm@selenic.com>
To: "David S. Miller" <davem@davemloft.net>, Jeff Moyer <jmoyer@redhat.com>
Cc: netdev@oss.sgi.com
Subject: Re: serious netpoll bug w/NAPI
Date: Wed, 9 Feb 2005 10:32:19 -0800 [thread overview]
Message-ID: <20050209183219.GA2366@waste.org> (raw)
In-Reply-To: <20050208201634.03074349.davem@davemloft.net>
On Tue, Feb 08, 2005 at 08:16:34PM -0800, David S. Miller wrote:
>
> Consider a NAPI device currently executing it's poll function,
> pushing SKBs into the networking stack.
>
> Some of these will generate response packets etc.
>
> If for some reason a printk() is generated by the packet processing
> and:
>
> 1) the netconsole output device is the same as the NAPI device
> processing packets
>
> 2) netif_queue_stopped() is true because the tx queue is full
>
> the netpoll code will recurse back into the driver's poll function.
> This is incredibly illegal and results in all kinds of driver state
> corruption. ->poll() must execute only once at a time.
On closer inspection, there's a couple other related failure cases
with the new ->poll logic in netpoll. I'm afraid it looks like
CONFIG_NETPOLL will need to guard ->poll() with a per-device spinlock
on netpoll-enabled devices.
This will mean putting a pointer to struct netpoll in struct
net_device (which I should have done in the first place) and will take
a few patches to sort out.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2005-02-09 18:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 4:16 serious netpoll bug w/NAPI David S. Miller
2005-02-09 18:32 ` Matt Mackall [this message]
2005-02-10 0:46 ` David S. Miller
2005-02-10 1:11 ` Matt Mackall
2005-02-10 9:16 ` Martin Josefsson
2005-02-10 17:14 ` Matt Mackall
2005-02-15 22:49 ` Jeff Moyer
2005-02-16 5:07 ` Matt Mackall
2005-02-16 19:26 ` Jeff Moyer
2005-02-16 22:07 ` Jeff Moyer
2005-02-16 23:02 ` David S. Miller
2005-02-16 23:44 ` Matt Mackall
2005-02-16 23:54 ` David S. Miller
2005-02-17 0:15 ` Matt Mackall
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=20050209183219.GA2366@waste.org \
--to=mpm@selenic.com \
--cc=davem@davemloft.net \
--cc=jmoyer@redhat.com \
--cc=netdev@oss.sgi.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).