From: Jarek Poplawski <jarkao2@o2.pl>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
"David S\. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [NETPOLL] netconsole: fix soft lockup when removing module
Date: Mon, 2 Jul 2007 13:08:01 +0200 [thread overview]
Message-ID: <20070702110801.GD1639@ff.dom.local> (raw)
In-Reply-To: <20070702092408.GA137@tv-sign.ru>
On Mon, Jul 02, 2007 at 01:24:08PM +0400, Oleg Nesterov wrote:
> On 07/02, Jarek Poplawski wrote:
> >
> > > > --- a/net/core/netpoll.c
> > > > +++ b/net/core/netpoll.c
> > > > @@ -72,7 +72,8 @@ static void queue_process(struct work_struct *work)
> > > > netif_tx_unlock(dev);
> > > > local_irq_restore(flags);
> > > >
> > > > - schedule_delayed_work(&npinfo->tx_work, HZ/10);
> > > > + if (atomic_read(&npinfo->refcnt))
> > > > + schedule_delayed_work(&npinfo->tx_work, HZ/10);
> > > > return;
> > > > }
> >
> > [...snip...]
> >
> > So, 2.6.21 needs something better (maybe you've found it btw.?),
> > but they weren't too interested, anyway.
>
> We can do a double flush trick. If queue_process() checks ->refcnt before
> schedule_delayed_work() like above, netpoll_cleanup() can do
>
> flush_scheduled_work();
>
> // the next invocation of queue_process()
> // must see ->refcnt == 0
> if (!cancel_delayed_work(&npinfo->tx_work)) {
> /* may be queued, wait for completion */
> flush_scheduled_work();
> }
I'll try to think about it later, but I don't plan to do next patch,
so feel free to send this. I didn't plan to fix netpoll at all
(I never didn't use nor studied this before...). But couldn't stand
this stupid lockup stays in 2.6.21. Now, I see it probably doesn't
annoy more than 2 or 3 people around...
>
> Jarek, I don't understand net/, a silly question. Why do we need the #2 chunk?
> Isn't it better to move skb_queue_purge(&npinfo->txq) after cancel_..._work()
> instead?
I've thought about this too, but because I don't know netpoll/netconsole
enough I didn't want to change more than minimum needed.
skb_queue_purge() uses heavy locking (irqsave) and I don't remember now
if I've found the reason or simply believed somebody had to have a reason
to do this there, anyway, if moved after cancel_ it could be done without
this locking, and something like while () instead of my if () should be
enough.
But there was not much interest about this patch, and I'm not currently
interested to be the main netconsole expert too, so maybe you would
like to try...
Cheers,
Jarek P.
next prev parent reply other threads:[~2007-07-02 10:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070701173558.GA207@tv-sign.ru>
2007-07-02 6:34 ` [NETPOLL] netconsole: fix soft lockup when removing module Jarek Poplawski
2007-07-02 9:24 ` Oleg Nesterov
2007-07-02 11:08 ` Jarek Poplawski [this message]
2007-07-02 7:52 ` [PATCH] " Jarek Poplawski
2007-07-02 8:59 ` Oleg Nesterov
2007-07-02 10:12 ` [PATCH 2/2][NETPOLL] netconsole: delete flush_scheduled_work Jarek Poplawski
2007-07-04 6:41 ` [PATCH] Re: [NETPOLL] netconsole: fix soft lockup when removing module Jarek Poplawski
2007-07-04 6:47 ` David Miller
2007-07-04 7:08 ` Jarek Poplawski
2007-07-04 7:21 ` 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=20070702110801.GD1639@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=torvalds@linux-foundation.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).