linux-kernel - Re: [PATCH] consider stack access while checking for alternate signal stack

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: <20091019080239.GB25783@Chamillionaire.breakpoint.cc>
Date:	Mon, 19 Oct 2009 10:02:39 +0200
From:	Sebastian Andrzej Siewior <sebastian@...akpoint.cc>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Sebastian Andrzej Siewior <sebastian@...akpoint.cc>,
	Roland McGrath <roland@...hat.com>,
	Oleg Nesterov <oleg@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org,
	Haavard Skinnemoen <hskinnemoen@...el.com>
Subject: Re: [PATCH] consider stack access while checking for alternate
 signal stack

* Ingo Molnar | 2009-10-19 09:33:58 [+0200]:

>> index 35e3bd9..520c489 100644
>> --- a/arch/avr32/Kconfig
>> +++ b/arch/avr32/Kconfig
>> @@ -70,6 +70,9 @@ config GENERIC_BUG
>>  	def_bool y
>>  	depends on BUG
>>  
>> +config STACK_STORE_POST
>> +	def_bool y
>> +
>>  source "init/Kconfig"
>>  
>>  source "kernel/Kconfig.freezer"
Haavard just nacked that part as I mixed up the 8bit AVR with the 32bit
version which is POST_DEC as well as the architectures. In that case
there are no POST_* architectures available.
So the question is should I leave dead code for further reference or
just remove it?

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