From: Kees Cook <keescook@chromium.org>
To: Danny Lin <danny@kdrag0n.dev>
Cc: Arnd Bergmann <arnd@arndb.de>,
Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Sami Tolvanen <samitolvanen@google.com>,
Fangrui Song <maskray@google.com>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com, stable@vger.kernel.org
Subject: Re: [PATCH] vmlinux.lds.h: Coalesce transient LLVM dead code elimination sections
Date: Thu, 2 Jul 2020 08:54:53 -0700 [thread overview]
Message-ID: <202007020853.5F15B5DDD@keescook> (raw)
In-Reply-To: <20200702085400.2643527-1-danny@kdrag0n.dev>
On Thu, Jul 02, 2020 at 01:54:00AM -0700, Danny Lin wrote:
> A recent LLVM 11 commit [1] made LLD stop implicitly coalescing some
> temporary LLVM sections, namely .{data,bss}..compoundliteral.XXX:
>
> [30] .data..compoundli PROGBITS ffffffff9ac9a000 19e9a000
> 000000000000cea0 0000000000000000 WA 0 0 32
> [31] .rela.data..compo RELA 0000000000000000 40965440
> 0000000000001d88 0000000000000018 I 2238 30 8
> [32] .data..compoundli PROGBITS ffffffff9aca6ea0 19ea6ea0
> 00000000000033c0 0000000000000000 WA 0 0 32
> [33] .rela.data..compo RELA 0000000000000000 409671c8
> 0000000000000948 0000000000000018 I 2238 32 8
> [...]
> [2213] .bss..compoundlit NOBITS ffffffffa3000000 1d85c000
> 00000000000000a0 0000000000000000 WA 0 0 32
> [2214] .bss..compoundlit NOBITS ffffffffa30000a0 1d85c000
> 0000000000000040 0000000000000000 WA 0 0 32
> [...]
>
> While these extra sections don't typically cause any breakage, they do
> inflate the vmlinux size due to the overhead of storing metadata for
> thousands of extra sections.
>
> It's also worth noting that for some reason, some downstream Android
> kernels can't boot at all if these sections aren't coalesced.
>
> This issue isn't limited to any specific architecture; it affects arm64
> and x86 if CONFIG_LD_DEAD_CODE_DATA_ELIMINATION is forced on.
>
> Example on x86 allyesconfig:
> Before: 2241 sections, 1170972 KiB
> After: 56 sections, 1171169 KiB
>
> [1] https://github.com/llvm/llvm-project/commit/9e33c096476ab5e02ab1c8442cc3cb4e32e29f17
>
> Link: https://github.com/ClangBuiltLinux/linux/issues/958
> Cc: stable@vger.kernel.org # v4.4+
> Suggested-by: Fangrui Song <maskray@google.com>
> Signed-off-by: Danny Lin <danny@kdrag0n.dev>
> ---
> include/asm-generic/vmlinux.lds.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/asm-generic/vmlinux.lds.h b/include/asm-generic/vmlinux.lds.h
> index db600ef218d7..18968cba87c7 100644
> --- a/include/asm-generic/vmlinux.lds.h
> +++ b/include/asm-generic/vmlinux.lds.h
> @@ -94,10 +94,10 @@
> */
> #ifdef CONFIG_LD_DEAD_CODE_DATA_ELIMINATION
> #define TEXT_MAIN .text .text.[0-9a-zA-Z_]*
> -#define DATA_MAIN .data .data.[0-9a-zA-Z_]* .data..LPBX*
> +#define DATA_MAIN .data .data.[0-9a-zA-Z_]* .data..LPBX* .data..compoundliteral*
> #define SDATA_MAIN .sdata .sdata.[0-9a-zA-Z_]*
> #define RODATA_MAIN .rodata .rodata.[0-9a-zA-Z_]*
> -#define BSS_MAIN .bss .bss.[0-9a-zA-Z_]*
> +#define BSS_MAIN .bss .bss.[0-9a-zA-Z_]* .bss..compoundliteral*
Are there .data.. and .bss.. sections we do NOT want to collect? i.e.
why not include .data..* and .bss..* ?
--
Kees Cook
next prev parent reply other threads:[~2020-07-02 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 8:54 [PATCH] vmlinux.lds.h: Coalesce transient LLVM dead code elimination sections Danny Lin
2020-07-02 15:54 ` Kees Cook [this message]
2020-07-02 16:04 ` Nathan Chancellor
2020-07-02 22:01 ` Danny Lin
2020-07-02 23:27 ` [PATCH v2] " Danny Lin
2020-07-10 14:03 ` Sasha Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202007020853.5F15B5DDD@keescook \
--to=keescook@chromium.org \
--cc=arnd@arndb.de \
--cc=clang-built-linux@googlegroups.com \
--cc=danny@kdrag0n.dev \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maskray@google.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=samitolvanen@google.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).