linux-kernel - Re: [GIT PULL] SLAB changes for v2.6.39-rc1

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 24 Mar 2011 21:29:06 +0200
From:	Pekka Enberg <penberg@...nel.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Christoph Lameter <cl@...ux.com>, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, tj@...nel.org, npiggin@...nel.dk,
	rientjes@...gle.com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: [GIT PULL] SLAB changes for v2.6.39-rc1

On Thu, Mar 24, 2011 at 9:27 PM, Ingo Molnar <mingo@...e.hu> wrote:
>
> * Pekka Enberg <penberg@...nel.org> wrote:
>
>> >From dd1534455196d2a8f6c9c912db614e59986c9f0e Mon Sep 17 00:00:00 2001
>> From: Pekka Enberg <penberg@...nel.org>
>> Date: Thu, 24 Mar 2011 19:59:35 +0200
>> Subject: [PATCH] x86: Early boot alternative instructions
>
> hm, patch is whitespace damaged.
>
> Also, the fix looks rather intrusive.
>
> Could we please disable the lockless slub code first and then do everything
> with proper testing and re-enable the lockless code *after* we know that the
> alternatives fixup change is robust, etc? That way there's no rush needed.
>
> There's a lot of code that could break from tweaking the alternatives code.

Just ignore this patch. As explained by Christoph, if alternative_io()
was the issue, we'd see the crash in kmem_cache_alloc().
--
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/