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-next>] [day] [month] [year] [list]
Message-Id: <200708122250.58773.jesper.juhl@gmail.com>
Date:	Sun, 12 Aug 2007 22:50:58 +0200
From:	Jesper Juhl <jesper.juhl@...il.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Paul Mundt <lethal@...ux-sh.org>, David Chinner <dgc@....com>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	Jan Engelhardt <jengelh@...putergmbh.de>,
	Matt Mackall <mpm@...enic.com>,
	Rene Herman <rene.herman@...il.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	William Lee Irwin III <wli@...omorphy.com>,
	Bodo Eggert <7eggert@....de>,
	Jesper Juhl <jesper.juhl@...il.com>
Subject: [PATCH 0/5] 4KSTACKS no longer a debug feature and doesn't belong in "Kernel hacking".

Hi,

The short story:
This is a series of 5 patches to a) lift 4KSTACKS from a debug feature to a 
non-debug feature and b) move it out of the Kernel hacking menu and into the 
Processor types and features menu and c) make it 'default y', but only 
for -mm.

Some more explanation is probably needed, so here's the longer story:
About a month back I posted a RFC patch with the subject 
"[PATCH][RFC] 4K stacks default, not a debug thing any more...?" to find out 
if I was right in assuming that 4K stacks were no longer considered a debug 
only feature and whether or not it would be sensible to make them default. 
You can find the head of the thread (100+ mesages) in the lkml.org archives 
here: http://lkml.org/lkml/2007/7/11/294 .

Based on the comments in that thread I conclude that 4KSTACKS are not really 
considered a debug-only feature any longer, but the time is not right (yet) 
to make them the default - and it's certainly not yet the time to get rid of 
8K stacks.

In that thread I promised to provide some patches that would lift 4KSTACKS out 
of debug-only feature status, which is what the first two patches in this 
series do.
I also said I would provide a patch to make 4KSTACKS 'default y' to get more 
testing, but restrict that patch to -mm - that's the fifth patch in this 
series.
Patches 3 & 4 in this series move the config option out of the Kernel hacking 
menu and into Processor types and features - this makes sense once it is no 
longer a debug feature and the location is in line with m68knommu (which is 
the only arch with this config symbol in addition to i386 & sh) which already 
place that symbol there.

Now for a bit on the actual patches. These are the patches in this series : 

[PATCH 1/5] 4KSTACKS, remove DEBUG_KERNEL dependency for i386
[PATCH 2/5] 4KSTACKS, remove DEBUG_KERNEL dependency for sh
[PATCH 3/5] 4KSTACKS, move out of Kernel hacking menu (i386)
[PATCH 4/5] 4KSTACKS, move out of Kernel hacking menu (sh)
[PATCH 5/5] 4KSTACKS, make 'default y', -mm patch only.

Andrew; as i386 & -mm maintainer I'm sending you patches 1, 3 & 5 - patches 2 
& 4 for Super-H I would like a maintainer ACK on before they go further, so 
I'm not Cc'ing you on those (they are on LKML if you want them anyway).

Paul; in the thread I mention above I was focusing 100% on i386. I don't 
really know the status of 4KSTACKS on sh, so I'd like your input.

I'm adding a few people from the previous thread to Cc, but far from everyone 
as then the Cc list would become too big. For the patches themselves I'm just 
sending them to LKML, Andrew & Paul, so pick them up on LKML please (sending 
as replies to this mail).


Kind regards,
  Jesper Juhl


-
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