linux-kernel - Re: [v2.6.26] what's brewing in x86.git for v2.6.26

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]

Message-ID: <84144f020804170341x44b3ac90h4fbfd193939af945@mail.gmail.com>
Date:	Thu, 17 Apr 2008 13:41:26 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Andrew Morton" <akpm@...ux-foundation.org>
Cc:	"Ingo Molnar" <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Vegard Nossum" <vegard.nossum@...il.com>
Subject: Re: [v2.6.26] what's brewing in x86.git for v2.6.26

Hi Andrew,

On Thu, Apr 17, 2008 at 1:33 PM, Andrew Morton
<akpm@...ux-foundation.org> wrote:
>  Thank you whoever wrote kmemcheck.txt

That would be Vegard.

On Thu, Apr 17, 2008 at 1:33 PM, Andrew Morton
<akpm@...ux-foundation.org> wrote:
>  How come slub uses one byte to track the status of each byte when it could
>  use a single bit?

Single bit is not enough as we track use after free as well (after
we've added delayed freeing to the beast).

On Thu, Apr 17, 2008 at 1:33 PM, Andrew Morton
<akpm@...ux-foundation.org> wrote:
>  We (still!) have not made the decision whether to proceed with slab or
>  slub.  How hard would it be to port kmemcheck into slab?

Not hard.
--
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/