From: Andre Noll <maan@systemlinux.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Linux 2.6.22-rc7
Date: Tue, 3 Jul 2007 18:46:26 +0200 [thread overview]
Message-ID: <20070703164626.GZ22589@skl-net.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0707030921400.4810@schroedinger.engr.sgi.com>
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
On 09:31, Christoph Lameter wrote:
> > Andre, does that simple change fix it for you (move the
> > "local_irq_enable()" to the end of early_kmem_cache_node_alloc)?
>
> Yes that should make the lock checker happy since interrupts are disabled
> when calling add_partial(). local_irq_enable can be called later without a
> problem. Useless longer interrupt hold off though.
I can confirm that the message disappears if local_irq_enable() is moved
to the end of the function.
> SLUB: Make lockdep happy by not calling add_partial with interrupts
> enabled during bootstrap
>
> If we move the local_irq_enable() to the end of the function then
> add_partial() in early_kmem_cache_node_alloc() will be called
> with interrupts disabled like during regular operations.
>
> Signed-off-by: Christoph Lameter <clameter@sgi.com>
Tested-By: Andre Noll <maan@systemlinux.org>
Thanks for the quick response and the fix, Linus and Christoph.
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-03 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 21:32 Linus Torvalds
2007-07-03 15:55 ` Andre Noll
2007-07-03 16:17 ` Linus Torvalds
2007-07-03 16:31 ` Christoph Lameter
2007-07-03 16:46 ` Andre Noll [this message]
2007-07-03 19:45 ` Ingo Molnar
2007-07-03 19:52 ` Christoph Lameter
2007-07-03 20:19 ` Ingo Molnar
2007-07-03 16:14 Martin Knoblauch
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=20070703164626.GZ22589@skl-net.de \
--to=maan@systemlinux.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®