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:	Thu, 12 Jul 2007 22:24:01 +0200
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"Ray Lee" <ray-lk@...rabbit.org>
Cc:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH][RFC] 4K stacks default, not a debug thing any more...?

On 12/07/07, Ray Lee <ray-lk@...rabbit.org> wrote:
> On 7/11/07, Jesper Juhl <jesper.juhl@...il.com> wrote:
> > I'm wondering if it's time to make 4K stacks the default and to start
> > considering removing the 8K stack option alltogether soon?
>
> Why? Leaving the option for 8k stacks isn't killing any kittens, AFAICS.
>
Well, as long as 8K stacks are an option we'll never get all the code
that doesn't work properly with 4K stacks fixed. We *might* get all
the in-tree code fixed eventually, but there's still going to be lots
of out-of-tree code that will keep depending on 8K stacks. And as long
as 4K stacks are not reliable, distributions are stick with 8K for
their kernels, people who build their own kernel are probably also
going to stick to 8K most of the time, since that's the default.  This
makes the 4K stack option fairly pointless for most users.

If we consider 4K stacks broken, not used much, then we should just
get rid of that option. That would remove a config choice (of which we
have IMHO way too many already) and it would remove code that we then
no longer need to maintain.

If, on the other hand, we consider 4K stacks to be the superior
solution, then we should work to get all code fixed to be able to
handle it so that it's actually something distros will start to enable
so that we can eventually get rid of the 8K stack option alltogether.
Making 4K stacks default and no longer a debug option is just the
first step in that direction.


-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
-
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