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: <2c0942db0707172339o2e4950e0p17cd0f9b631e5311@mail.gmail.com>
Date:	Tue, 17 Jul 2007 23:39:00 -0700
From:	"Ray Lee" <ray-lk@...rabbit.org>
To:	"Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc:	"Rene Herman" <rene.herman@...il.com>,
	"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/17/07, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> On Mon, 16 Jul 2007 16:15:28 -0700
> "Ray Lee" <ray-lk@...rabbit.org> wrote:
> > Heh :-). No, it's not a question of trust. First and foremost, it's
> > that there are still users who say that they can crash a current
> > 4k+interrupt stacks kernel, while the 8k without interrupt stacks is
> > fine.
>
> You forgot "most of the time".

Yeah, fair enough.

> Its statistically less likely, which
> merely means its evilly hard to debug

Not being able to debug the cases that occur (and the fact that
they're rare, as you're pointing out) is as much of a problem as the
crashes themselves. 8k + IRQ stacks with a warning when 4k of process
stack is exceeded would seem like a reasonable first step to making 4k
a palatable default.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ