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: <4696FC43.3000201@goop.org>
Date:	Thu, 12 Jul 2007 21:14:59 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Jesper Juhl <jesper.juhl@...il.com>
CC:	Ray Lee <ray-lk@...rabbit.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	William Lee Irwin III <wli@...omorphy.com>,
	David Chinner <dgc@....com>
Subject: Re: [PATCH][RFC] 4K stacks default, not a debug thing any more...?

Jesper Juhl wrote:
> Yes and no.  If that will get things moving in the direction of
> getting rid of the stack size as a config option, then I'm all for it.
> But on the other hand it is my personal opinion that this is an area
> where we should just make up our minds as to whether we want 4K or 8K
> stacks and whether we want interrupt stacks or not, and then not have
> it configurable at all.  

Well, smaller stacks are better where possible, but there's nothing 
magic about 4k.  Sure, its mostly enough, but there's no particular 
reason to believe it will be enough for everything.  You could state a 
priori that all kernel code paths must fit into 4k of stack, but that's 
pretty arbitrary.

I'm tempted to post a patch making XFS depend on 8K stacks.  I know is 
simplistic, given that it seems to be xfs+lvm which is particularly 
problematic, and other filesystems+lvm are also a problem.  But its 
better than crashing.

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