From: Jarek Poplawski <jarkao2@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
marcus@better.se,
Stephen Hemminger <shemminger@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [Bugme-new] [Bug 10326] New: inconsistent lock state in net_rx_action
Date: Thu, 27 Mar 2008 11:07:00 +0100 [thread overview]
Message-ID: <20080327100700.GA2845@ami.dom.local> (raw)
In-Reply-To: <20080327021812.601776b8.akpm@linux-foundation.org>
On Thu, Mar 27, 2008 at 02:18:12AM -0700, Andrew Morton wrote:
...
> Anyway, the accusation is that lockdep is busted, in that it doesn't realise that
> local_irq_disable() blocks softirqs.
Usually lockdep gets this right, so I've some doubts too. But here
it's not only about softirqs; this:
> >> Mar 25 19:48:46 better kernel: #1: (target_list_lock){--..}, at: [<c0399c0d>]
means lockdep saw hardirqs enabled while acquiring/holding this lock.
Jarek P.
next prev parent reply other threads:[~2008-03-27 10:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10326-10286@http.bugzilla.kernel.org/>
2008-03-25 20:43 ` [Bugme-new] [Bug 10326] New: inconsistent lock state in net_rx_action Andrew Morton
2008-03-26 23:13 ` Jarek Poplawski
2008-03-27 0:14 ` Andrew Morton
2008-03-27 8:55 ` Jarek Poplawski
2008-03-27 9:08 ` Jarek Poplawski
2008-03-27 9:18 ` Andrew Morton
2008-03-27 10:07 ` Jarek Poplawski [this message]
2008-03-27 10:56 ` Peter Zijlstra
2008-03-27 11:03 ` David Miller
2008-03-27 11:59 ` Marcus Better
2008-03-27 12:32 ` Jarek Poplawski
2008-03-27 21:44 ` David Miller
2008-03-27 12:22 ` Jarek Poplawski
2008-03-27 12:30 ` Peter Zijlstra
2008-03-27 12:49 ` Jarek Poplawski
2008-03-27 21:56 ` Rafael J. Wysocki
2008-03-27 22:22 ` Jarek Poplawski
2008-03-27 22:22 ` David Miller
2008-03-27 22:39 ` Jarek Poplawski
2008-03-28 0:59 ` David Miller
2008-03-28 10:12 ` Peter Zijlstra
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=20080327100700.GA2845@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus@better.se \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=shemminger@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.