linux-kernel - Re: [PATCH RFC] x86: enforce inlining for atomics

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]

Date:	Mon, 13 Jul 2015 20:25:04 +0200
From:	Denys Vlasenko <vda.linux@...glemail.com>
To:	Markus Trippelsdorf <markus@...ppelsdorf.de>
Cc:	Hagen Paul Pfeifer <hagen@...u.net>,
	Ingo Molnar <mingo@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Borislav Petkov <bp@...en8.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH RFC] x86: enforce inlining for atomics

On Wed, Apr 22, 2015 at 11:20 AM, Markus Trippelsdorf
<markus@...ppelsdorf.de> wrote:
> On 2015.04.22 at 07:58 +0200, Hagen Paul Pfeifer wrote:
>> * Markus Trippelsdorf | 2015-04-22 07:24:41 [+0200]:
>> >I cannot reproduce this issue with my config with 4.8, 4.9 or 5. Could
>> >you please come up with a small testcase and open a gcc bug (with full
>> >gcc command line)?
>>
>> the attached config file should do the trick. Can you try it?
>
> It is definitely a -O2 vs. -Os issue. With your config:


It's true that it happens more often with -Os, but -O2 is not immune either.

See comments in the gcc bug:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66122
--
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/