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 23:06:02 +0200
From:	Denys Vlasenko <vda.linux@...glemail.com>
To:	Hagen Paul Pfeifer <hagen@...u.net>
Cc:	Ingo Molnar <mingo@...nel.org>, Borislav Petkov <bp@...en8.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH RFC] x86: enforce inlining for atomics

On Mon, Jul 13, 2015 at 9:20 PM, Hagen Paul Pfeifer <hagen@...u.net> wrote:
>> On July 13, 2015 at 8:27 PM Denys Vlasenko <vda.linux@...glemail.com>
>> wrote:
>
>> > So I think the original patch makes sense (and I already applied it),
>> > we want known-simple and performance critical methods (such as atomic
>> > ops) always inlined.
>>
>> I will send more such force-inlining patches your way then.
>
> Now? We discuss this a month back or so? :-)

Not *your* way.
I meant that I'll send patches to Ingo - I see that he agrees that
this worth fixing instead of waiting for a better compiler.

(Ideally, the compiler shouldn't do this, but gcc BZ comments
are not encouraging).
--
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/