All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci0f5f89ea9f7f1dc5@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: kallsyms: optimise symbol search by name
Date: Sun, 18 Oct 2026 10:48:24 -0700	[thread overview]
Message-ID: <6ad50668.7f4e89eb.3d59aa.00b6.GAE@google.com> (raw)

syzbot ci has tested the following series

[v2] kallsyms: optimise symbol search by name
https://lore.kernel.org/all/20261018155206.132411-1-david.laight.linux@gmail.com
* [PATCH v2 next 01/15] kallsyms: scripts/kallsyms.c: Avoid overrunning on-stack buffer
* [PATCH v2 next 02/15] kallsyms: Fix selftest startup delay
* [PATCH v2 next 03/15] kallsyms: Improve selftest test_perf_kallsyms_lookup_name() output
* [PATCH v2 next 04/15] kallsyms: scripts/kallsyms: Check for output file write errors
* [PATCH v2 next 05/15] kallsyms: Match compressed tokens on the fly during binary search
* [PATCH v2 next 06/15] kallsyms: Optimise symbol name search
* [PATCH v2 next 07/15] kallsyms: Optimise detection of duplicate symbol names
* [PATCH v2 next 08/15] kallsyms: Support changing the density of the kallsyms_markers[] array
* [PATCH v2 next 09/15] kallsyms: Add a kernel parameter for the marker shift
* [PATCH v2 next 10/15] kallsyms: scripts/kallsyms: Rename some variables for clarity
* [PATCH v2 next 11/15] kallsyms: scripts/kallsyms: Keep full expansion of tokens
* [PATCH v2 next 12/15] kallsyms: scripts/kallsyms: Optimise compress_symbols()
* [PATCH v2 next 13/15] kallsyms: scripts/kallsyms: Reuse tokens that have no references
* [PATCH 14/15] kallsyms: scripts/kallsyms: Reduce the output file size
* [PATCH 15/15] kallsyms: scripts/kallsyms: Improve compression by about 2%

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/b38c1cac-393b-482e-8fc6-3608acd56bbe

***

kernel build error

tree:      bpf-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base:      cee9395acd8043be0644b25c34bfa86623f2b935
arch:      amd64
compiler:  Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
config:    https://ci.syzbot.org/builds/125a8c98-5370-4a3f-8594-fda40dba54a1/config

timedout after 1h0m0s ["make" "KERNELVERSION=syzkaller" "KERNELRELEASE=syzkaller" "LOCALVERSION=-syzkaller" "-j" "48" "ARCH=x86_64" "LLVM=1" "bzImage"]

***

If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
  Tested-by: syzbot@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.

To test a fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.

Notes:
- The patch will be applied on top of the tested series (as an
  incremental fix).
- To test a new version of the whole series, please send it directly
  to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.

The email will later be sent to:
[akpm@linux-foundation.org andrey.grodzovsky@crowdstrike.com bpf@vger.kernel.org david.laight.linux@gmail.com jim.cromie@gmail.com kees@kernel.org linux-kbuild@vger.kernel.org linux-kernel@vger.kernel.org ljs@kernel.org mcgrof@kernel.org pmladek@suse.com rostedt@goodmis.org]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid


                 reply	other threads:[~2026-10-18 17:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6ad50668.7f4e89eb.3d59aa.00b6.GAE@google.com \
    --to=syzbot+ci0f5f89ea9f7f1dc5@syzkaller.appspotmail.com \
    --cc=syzbot@lists.linux.dev \
    --cc=syzkaller-upstream-moderation@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.