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]

Message-ID: <2c0942db0707161640h3c3afd7avecd7b3c61c4e7df1@mail.gmail.com>
Date:	Mon, 16 Jul 2007 16:40:53 -0700
From:	"Ray Lee" <ray-lk@...rabbit.org>
To:	"Rene Herman" <rene.herman@...il.com>
Cc:	"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 7/16/07, Rene Herman <rene.herman@...il.com> wrote:
> On 07/17/2007 01:13 AM, Ray Lee wrote:
> > Given that there's actual, y'know, reports of people who can easily
> > crash a 4k+interrupt stacks kernel, and not an 8k one, I think the
> > current evidence speaks for itself.
>
> Where?

The second message in this thread, according to my reader, from Zan
Lynx. Another from Utz Lehmann a few minutes ago.

> > The point remains that the burden of proof of the safety of the 4k only
> > option is upon those people who want to remove the 8k option.
>
> Removing any such option was not the objective of this thread, just lifting
> 4K stacks from debug and making it the default.

True, but your messages are reading as advocacy for removing the 8k
option. I'm saying that's a bad idea. If I misunderstood your
position, then my bad.

> People fortunate enough to
> use workloads where some piece of crap code by accident works more often
> with the current shared 8K stacks then it does with the unshared 4K stacks
> can then still nicely not select it (or fix the code if possible).

If they even realize that it's the cause of the problem. In the
meantime, we're generating more bug reports to lkml. As the general
opinion is that the ones getting received now aren't getting enough
attention (see regression tracking threads), setting a default that is
known to break setups in hard to debug ways seems counterproductive.
-
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/