linux-kernel - Re: [PATCH -mm] slub: update cpu after new

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0704250920100.26221@schroedinger.engr.sgi.com>
Date:	Wed, 25 Apr 2007 09:21:56 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Hugh Dickins <hugh@...itas.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm] slub: update cpu after new_slab()

On Wed, 25 Apr 2007, Hugh Dickins wrote:

> But, surely you wouldn't have expected it to stay on the processor
> throughout the waiting page allocation??  I think you're misremembering
> your expectations, and this was just a simple, understandable, oversight.

You do not know my fuzzy brain... Some thoughts go wrong once and 
twice and then are stuck in there and I need people like you to 
straighten me out.

> Quite a serious one, though: it got caught in my case by the NULL
> dereference, but it's probably been switching cpu there much more
> often - one cpu diddling with what's private to another, with
> unpredictable results.

Right. Thanks for catching it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/