linux-kernel - Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3

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: <ebf06e6c083df46dabc15454dcd89362@kernel.crashing.org>
Date:	Mon, 6 Aug 2007 23:15:08 +0200
From:	Segher Boessenkool <segher@...nel.crashing.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Willy Tarreau <w@....eu>, Axel Reinhold <axel@...akout.de>,
	linux-kernel@...r.kernel.org
Subject: Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3

> Well, top-level assembly is usually nasty.  Setting the section in the
> assembly statement as you said is probably the only thing you *can* do.

You'll probably need to (at the end of the asm block) restore
the current section to what it was before (".previous"), too.

> I don't think there is any requirement that top-level assembly
> statements get the section set to .text on their behalf.

Correct.


Segher

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