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: [PATCH] Re: [NETPOLL] netconsole: fix soft lockup when removing module
Date: Wed, 4 Jul 2007 08:41:59 +0200 [thread overview]
Message-ID: <20070704064159.GA2057@ff.dom.local> (raw)
In-Reply-To: <20070702075226.GB1639@ff.dom.local>
On Mon, Jul 02, 2007 at 09:52:26AM +0200, Jarek Poplawski wrote:
>
> From my recent patch:
>
> > > #1
> > > Until kernel ver. 2.6.21 (including) cancel_rearming_delayed_work()
> > > required a work function should always (unconditionally) rearm with
> > > delay > 0 - otherwise it would endlessly loop. This patch replaces
> > > this function with cancel_delayed_work(). Later kernel versions don't
> > > require this, so here it's only for uniformity.
>
> But Oleg Nesterov <oleg@tv-sign.ru> found:
>
> > But 2.6.22 doesn't need this change, why it was merged?
> >
> > In fact, I suspect this change adds a race,
> ...
>
> His description was right (thanks), so this patch reverts #1.
>
> Signed-off-by: Jarek Poplawski <jarkao2@o2.pl>
Oleg,
I think maybe you could ack these 2 netconsole patches...
They were done on your request but it looks like Andrew
is waiting on something...
Thanks,
Jarek P.
next prev parent reply other threads:[~2007-07-04 6:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 17:35 [NETPOLL] netconsole: fix soft lockup when removing module Oleg Nesterov
2007-07-02 6:34 ` Jarek Poplawski
2007-07-02 9:24 ` Oleg Nesterov
2007-07-02 11:08 ` Jarek Poplawski
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 ` Jarek Poplawski [this message]
2007-07-04 6:47 ` [PATCH] Re: [NETPOLL] netconsole: fix soft lockup when removing module 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=20070704064159.GA2057@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.