linux-kernel - Re: [patch 2/2] x86: lds - Use THREAD

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] [day] [month] [year] [list]

Message-Id: <200802181527.22502.ak@suse.de>
Date:	Mon, 18 Feb 2008 15:27:22 +0100
From:	Andi Kleen <ak@...e.de>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Cyrill Gorcunov <gorcunov@...il.com>,
	Sam Ravnborg <sam@...nborg.org>, mingo@...e.hu,
	tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [patch 2/2] x86: lds - Use THREAD_SIZE instead of numeric	constant


> You're saying that it *must* be aligned, I don't think that's true 
> anymore; I think nowadays it's more accurate to say that it *is* 
> aligned, but I don't think that's fundamental.

At least in .25 mainline current_thread_info() is still using
[re]sp arithmetic.  Also I think the stack backtracers also
rely on suitable alignment of the stack top. So right now it is still 
fundamental. Now that could be all fixed by using segment
register references and might be, but so far that doesn't
seem to be finished yet.


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