From: sashiko-bot@kernel.org
To: "David Laight" <david.laight.linux@gmail.com>,
"Petr Mladek" <pmladek@suse.com>, "Kees Cook" <kees@kernel.org>,
linux-kbuild@vger.kernel.org, bpf@vger.kernel.org,
"Jim Cromie" <jim.cromie@gmail.com>,
"Lorenzo Stoakes" <ljs@kernel.org>
Cc: "Luis Chamberlain" <mcgrof@kernel.org>,
"Andrey Grodzovsky" <andrey.grodzovsky@crowdstrike.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Samuel Wu" <wusamuel@google.com>,
nathan@kernel.org, nsc@kernel.org
Subject: Re: [PATCH v3 next 08/13] kallsyms: Optimise symbol name search
Date: Wed, 11 Nov 2026 12:59:51 +0000 [thread overview]
Message-ID: <sashiko-outbox-209030@kernel.org> (raw)
In-Reply-To: <20261111115911.1142000-9-david.laight.linux@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] kallsyms: broken 24-bit big-endian offset calculation in
write_src()
--
commit 129df190c855fc8323de3f8129f606cadccd6466
Author: David Laight <david.laight.linux@gmail.com>
kallsyms: Optimise symbol name search
This commit changes the alphabetically sorted symbol table from indexing
kallsyms_offsets to indexing the compressed kallsyms_names stream, with the
low bit indicating duplicate symbol names.
> diff --git a/scripts/kallsyms.c b/scripts/kallsyms.c
> index 74db751600b4f..930ec27a53c06 100644
> --- a/scripts/kallsyms.c
> +++ b/scripts/kallsyms.c
[ ... ]
> @@ -570,23 +571,41 @@ static void write_src(void)
> sort_symbols_by_name();
> stamp("sort by name");
>
> - output_label("kallsyms_seqs_of_names");
> - write_incbin_header("seq_of_names", &bin_offset);
> + off_size = table_size < (1u << 23) ? 24 : 32;
> + output_label("kallsyms_offs_of_names");
> + printf("\t.long\t%u\n", off_size);
> + write_incbin_header("offs_of_names", &bin_offset);
> for (i = 0; i < table_cnt; i++) {
> se = table[i];
> - seq = se->seq;
> + off = se->seq << 1;
> + if (i && se->len == table[i - 1]->len &&
> + !memcmp(se->sym + 1, table[i - 1]->sym + 1, se->len - 1))
> + /* Mark that this is a duplicate of the previous symbol */
> + off |= 1;
> if (out_bin_file) {
> - unsigned int seq_be = htobe32(seq);
> - fwrite((char *)&seq_be + 1, 1, 3, out_bin_file);
> + unsigned int off_te = big_endian ? htobe32(off) >> (32 - off_size): htole32(off);
> + fwrite(&off_te, 1, off_size / 8 , out_bin_file);
[Severity: High]
Does this corrupt the 24-bit entries written to out_bin_file when building
a big-endian kernel on a big-endian host?
On a big-endian host, htobe32(off) is a no-op, so shifting the result right
by 8 discards the low byte of off and leaves two leading zero bytes at the
start of off_te. fwrite(&off_te, 1, 3, out_bin_file) then emits two zero
bytes followed by only the most significant byte of the 24-bit entry,
breaking kallsyms_lookup_name() and kallsyms_on_each_match_symbol() at
runtime.
Shifting off before byte-swapping, as in htobe32(off << (32 - off_size)),
places the three big-endian bytes at the start of off_te on both
little-endian and big-endian hosts.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111115911.1142000-1-david.laight.linux@gmail.com?part=8
next prev parent reply other threads:[~2026-11-11 12:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 11:58 [PATCH v3 next 00/13] kallsyms: optimise symbol search by name David Laight
2026-11-11 11:58 ` [PATCH v3 next 01/13] scripts/kallsyms: Avoid overrunning on-stack buffer David Laight
2026-11-11 11:59 ` [PATCH v3 next 02/13] scripts/kallsyms: Improve error reporting David Laight
2026-11-11 12:14 ` sashiko-bot
2026-11-11 23:33 ` bot+bpf-ci
2026-11-11 11:59 ` [PATCH v3 next 03/13] scripts/elf-parse: add elf_map_big_endian() helper David Laight
2026-11-11 11:59 ` [PATCH v3 next 04/13] scripts/kallsyms: make use of binary data output optional David Laight
2026-11-11 12:32 ` sashiko-bot
2026-11-11 23:34 ` bot+bpf-ci
2026-11-11 11:59 ` [PATCH v3 next 05/13] kallsyms: Fix selftest startup delay David Laight
2026-11-11 12:36 ` sashiko-bot
2026-11-11 11:59 ` [PATCH v3 next 06/13] kallsyms: Improve selftest test_perf_kallsyms_lookup_name() output David Laight
2026-11-11 23:17 ` bot+bpf-ci
2026-11-11 11:59 ` [PATCH v3 next 07/13] kallsyms: Match compressed tokens on the fly during binary search David Laight
2026-11-11 12:46 ` sashiko-bot
2026-11-11 11:59 ` [PATCH v3 next 08/13] kallsyms: Optimise symbol name search David Laight
2026-11-11 12:59 ` sashiko-bot [this message]
2026-11-11 11:59 ` [PATCH v3 next 09/13] kallsyms: Add a kernel parameter to change the kallsyms_markers[] density David Laight
2026-11-11 13:07 ` sashiko-bot
2026-11-11 23:33 ` bot+bpf-ci
2026-11-11 11:59 ` [PATCH v3 next 10/13] scripts/kallsyms: Keep full expansion of tokens David Laight
2026-11-11 11:59 ` [PATCH v3 next 11/13] scripts/kallsyms: Optimise compress_symbols() David Laight
2026-11-11 11:59 ` [PATCH v3 next 12/13] scripts/kallsyms: Reuse tokens that have no references David Laight
2026-11-11 23:34 ` bot+bpf-ci
2026-11-11 11:59 ` [PATCH v3 next 13/13] scripts/kallsyms: Reuse little-used compression tokens David Laight
2026-11-11 13:37 ` sashiko-bot
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=sashiko-outbox-209030@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=andrey.grodzovsky@crowdstrike.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=jim.cromie@gmail.com \
--cc=kees@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=mcgrof@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wusamuel@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