From: Jessica Yu <jeyu@kernel.org>
To: Fangrui Song <maskray@google.com>
Cc: linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com,
Marco Elver <melver@google.com>
Subject: Re: [PATCH] module: Ignore _GLOBAL_OFFSET_TABLE_ when warning for undefined symbols
Date: Thu, 14 Jan 2021 15:06:22 +0100 [thread overview]
Message-ID: <20210114140621.GA15904@linux-8ccs> (raw)
In-Reply-To: <20210114054831.343327-1-maskray@google.com>
+++ Fangrui Song [13/01/21 21:48 -0800]:
>clang-12 -fno-pic (since
>https://github.com/llvm/llvm-project/commit/a084c0388e2a59b9556f2de0083333232da3f1d6)
>can emit `call __stack_chk_fail@PLT` instead of `call __stack_chk_fail`
>on x86. The two forms should have identical behaviors on x86-64 but the
>former causes GNU as<2.37 to produce an unreferenced undefined symbol
>_GLOBAL_OFFSET_TABLE_.
>
>(On x86-32, there is an R_386_PC32 vs R_386_PLT32 difference but the
>linker behavior is identical as far as Linux kernel is concerned.)
>
>Simply ignore _GLOBAL_OFFSET_TABLE_ for now, like what
>scripts/mod/modpost.c:ignore_undef_symbol does. This also fixes the
>problem for gcc/clang -fpie and -fpic, which may emit `call foo@PLT` for
>external function calls on x86.
>
>Note: ld -z defs and dynamic loaders do not error for unreferenced
>undefined symbols so the module loader is reading too much. If we ever
>need to ignore more symbols, the code should be refactored to ignore
>unreferenced symbols.
>
>Reported-by: Marco Elver <melver@google.com>
>Link: https://github.com/ClangBuiltLinux/linux/issues/1250
>Signed-off-by: Fangrui Song <maskray@google.com>
>---
> kernel/module.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
>diff --git a/kernel/module.c b/kernel/module.c
>index 4bf30e4b3eaa..2e2deea99289 100644
>--- a/kernel/module.c
>+++ b/kernel/module.c
>@@ -2395,8 +2395,14 @@ static int simplify_symbols(struct module *mod, const struct load_info *info)
> break;
> }
>
>- /* Ok if weak. */
>- if (!ksym && ELF_ST_BIND(sym[i].st_info) == STB_WEAK)
>+ /* Ok if weak. Also allow _GLOBAL_OFFSET_TABLE_:
>+ * GNU as before 2.37 produces an unreferenced _GLOBAL_OFFSET_TABLE_
>+ * for call foo@PLT on x86-64. If the code ever needs to ignore
>+ * more symbols, refactor the code to only warn if referenced by
>+ * a relocation.
>+ */
>+ if (!ksym && (ELF_ST_BIND(sym[i].st_info) == STB_WEAK ||
>+ !strcmp(name, "_GLOBAL_OFFSET_TABLE_")))
> break;
Hi Fangrui,
Thanks for the patch. I am puzzled why we don't already mirror modpost
here, that particular line of code in modpost to ignore _GLOBAL_OFFSET_TABLE_
has been there long before my time. Let's properly mirror modpost
then, and create a similar helper function ignore_undef_symbol() (and
stick the _GLOBAL_OFFSET_TABLE_ check in there) to account for future
cases like this.
Thanks,
Jessica
next prev parent reply other threads:[~2021-01-14 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 5:48 [PATCH] module: Ignore _GLOBAL_OFFSET_TABLE_ when warning for undefined symbols Fangrui Song
2021-01-14 14:06 ` Jessica Yu [this message]
2021-01-14 16:57 ` Fāng-ruì Sòng
2021-01-14 21:18 ` Jessica Yu
2021-01-14 21:54 ` [PATCH v2] " Fangrui Song
2021-01-14 22:01 ` Nick Desaulniers
2021-01-15 8:09 ` Jessica Yu
2021-01-15 7:03 ` Marco Elver
2021-01-15 8:14 ` Jessica Yu
2021-01-15 19:50 ` Fāng-ruì Sòng
2021-01-15 19:52 ` [PATCH v3] " Fangrui Song
2021-01-15 19:55 ` Nathan Chancellor
2021-01-18 10:14 ` Jessica Yu
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=20210114140621.GA15904@linux-8ccs \
--to=jeyu@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maskray@google.com \
--cc=melver@google.com \
/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