From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Daniel J Blueman" <daniel.blueman@gmail.com>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Christoph Lameter" <clameter@sgi.com>,
"Ingo Molnar" <mingo@elte.hu>,
"Pekka Enberg" <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] debugobjects: fix lockdep warning
Date: Sun, 15 Jun 2008 13:46:21 +0200 [thread overview]
Message-ID: <19f34abd0806150446s35ed1ffib9a7ab459f00e870@mail.gmail.com> (raw)
In-Reply-To: <6278d2220806150252h10230d2s775913c75d16b793@mail.gmail.com>
On Sun, Jun 15, 2008 at 11:52 AM, Daniel J Blueman
<daniel.blueman@gmail.com> wrote:
> On Sat, Jun 14, 2008 at 11:58 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
>> Hi,
>>
>> I don't know whether this is truly the Right Fix; if it isn't, feel free
>> to re-use my commit template for when the RF appears... ;-)
>>
>> Daniel, is there any chance you can try it out? Thanks.
>
> I get a warning [1] about pool-lock being IRQ-unsafe as-is.
> Additionally promoting pool_lock to be IRQ-safe [2] resolves the
> issue, but this may not be desired. Ping me for further tests and
> thanks!
Ah, yes. Thanks for testing! I thought it might introduce some other
badness. I can't really comment on your new changes (I am not sure
what the implications are exactly), but if it fixes the regression,
then it sounds correct :-)
(I also think this needs Thomas's SOB rather than mine. I am not sure
he's fine with kicking out the retry code :-P)
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
prev parent reply other threads:[~2008-06-15 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 22:58 Vegard Nossum
2008-06-15 9:52 ` Daniel J Blueman
2008-06-15 11:46 ` Vegard Nossum [this message]
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=19f34abd0806150446s35ed1ffib9a7ab459f00e870@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=clameter@sgi.com \
--cc=daniel.blueman@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®