linux-kernel - Re: [PATCH][RFC] 4K stacks default, not a debug thing any more...?

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:	Tue, 17 Jul 2007 01:05:12 +0200
From:	Rene Herman <rene.herman@...il.com>
To:	Ray Lee <ray-lk@...rabbit.org>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>, Bodo Eggert <7eggert@....de>,
	Matt Mackall <mpm@...enic.com>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	Jesper Juhl <jesper.juhl@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	William Lee Irwin III <wli@...omorphy.com>,
	David Chinner <dgc@....com>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: [PATCH][RFC] 4K stacks default, not a debug thing any more...?

On 07/17/2007 12:53 AM, Ray Lee wrote:

> On 7/16/07, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

>> Any x86-32 path unsafe with 4K stacks is almost certainly unsafe with 8K
>> stacks because the 8K stacks do not have seperate IRQ stack paths, so you
>> have the same space but split. It might be less predictable on 8K stacks
>> but it isn't absent.
> 
> Understood, but isn't that an argument pro interrupt stacks, rather
> than one against 8k? wli has a patch to break out the interrupt stack
> feature from the 4k/8k choice.

Yes but it's also an argument that the 4K stacks don't make the _current_ 
situation without CONFIG_4KSTACKS selected worse and given that you trust 
that current situation, that leaves you without your argument :-)

Rene.


-
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/