linux-kernel - Re: [BLOCK] bh: Ensure bh fits within a page

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: <20060801074556.b9e772bc.akpm@osdl.org>
Date:	Tue, 1 Aug 2006 07:45:56 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	linux-kernel@...r.kernel.org, ext2-devel@...ts.sourceforge.net
Subject: Re: [BLOCK] bh: Ensure bh fits within a page

On Tue, 1 Aug 2006 21:06:58 +1000
Herbert Xu <herbert@...dor.apana.org.au> wrote:

> On Mon, Jul 31, 2006 at 10:54:54PM -0700, Andrew Morton wrote:
> > 
> > Crap, that's hard to fix.   Am I allowed to blame submit_bh()? ;)
> 
> Sure you're allowed to do anything :)
> 
> > uhm, we don't want to lose kmalloc redzoning, so I guess we need to create
> > on-demand ext3-private slab caches for 1024, 2048, and 4096 bytes.  With
> > the appropriate slab flags to defeat the redzoning.
> 
> Either that or we should fix redzoning so that it actually preserves
> alignment, rather than turning off debugging whenever we want alignment.
> Basically it means that we need to use twice the amount of memory for
> each object (so 2K for each 1K object).  Is this acceptable for debugging?

It doesn't sound like a good idea.  At present CONFIG_DEBUG_SLAB is
acceptable for production use (although it makes kernel profiles look
pretty sad).  Doubling the size of the slabs would rather alter that.
-
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/