linux-kernel - Re: [PATCH] x86: force inlining of atomic ops

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:	Tue, 12 May 2015 09:57:08 +0200
From:	Hagen Paul Pfeifer <hagen@...u.net>
To:	Denys Vlasenko <dvlasenk@...hat.com>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Borislav Petkov <bp@...en8.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andy Lutomirski <luto@...capital.net>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Alexei Starovoitov <ast@...mgrid.com>,
	Will Drewry <wad@...omium.org>,
	Kees Cook <keescook@...omium.org>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: force inlining of atomic ops

* Denys Vlasenko | 2015-05-08 12:26:02 [+0200]:

[snip]
>With both gcc 4.7.2 and 4.9.2, sometimes gcc mysteriously doesn't inline
>This patch fixes this for x86 atomic ops via s/inline/__always_inline/.
>This decreases allyesconfig kernel by about 25k:
>
>    text     data      bss       dec     hex filename
>82399481 22255416 20627456 125282353 777a831 vmlinux.before
>82375570 22255544 20627456 125258570 7774b4a vmlinux

atomic_inc, atomic_sub, atomic_add, atomic_sub_and_test, atomic_dec,
atomic_dec_and_test, atomic_add_return, __atomic_add_unless, atomic64_add,
atomic64_inc, atomic64_dec, atomic64_add_return

are already annotated with __always_inline. This patch will lead to merge
conflicts someone, Ingo?

See https://lkml.org/lkml/2015/4/20/637

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