From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: hramrach@centrum.cz, netdev@vger.kernel.org,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, herbert@gondor.hengli.com.au
Subject: Re: [Bugme-new] [Bug 18492] New: kernel softirq warning on boot
Date: Tue, 14 Sep 2010 14:11:03 -0700 (PDT) [thread overview]
Message-ID: <20100914.141103.123996613.davem@davemloft.net> (raw)
In-Reply-To: <20100914135730.8af6bc76.akpm@linux-foundation.org>
From: Andrew Morton <akpm@linux-foundation.org>
Date: Tue, 14 Sep 2010 13:57:30 -0700
> On Tue, 14 Sep 2010 22:45:19 +0200
> Michal Suchanek <hramrach@centrum.cz> wrote:
>
>> > rcu_read_unlock_bh() in netpoll_rx(), added by "netpoll: Fix RCU
>> > usage".
>>
>> Do you mean de85d99eb7b595f6751550184b94c1e2f74a828b?
>
> yup.
>
>> I am not sure reverting just that would work, nor that the kernel
>> around that point is in shape for trying on a system I would want to
>> still use. It's way back in history for a kernel which is just to be
>> released.
>
> No, we wouldn't want to revert it - it fixes stuff.
>
> It could be that we just don't need the _bh locking, if local irqs are
> reliably disabled. But I didn't really look.
I'll take a closer look at this if Herbert doesn't beat me to it.
next prev parent reply other threads:[~2010-09-14 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-18492-10286@https.bugzilla.kernel.org/>
2010-09-14 19:07 ` [Bugme-new] [Bug 18492] New: kernel softirq warning on boot Andrew Morton
2010-09-14 20:45 ` Michal Suchanek
2010-09-14 20:57 ` Andrew Morton
2010-09-14 21:11 ` David Miller [this message]
2010-09-15 6:46 ` Herbert Xu
2010-09-16 4:40 ` David Miller
2010-09-17 18:00 ` Michal Suchanek
2010-09-17 23:55 ` David Miller
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=20100914.141103.123996613.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=herbert@gondor.hengli.com.au \
--cc=hramrach@centrum.cz \
--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).