From: syzbot ci <syzbot+ci5443f6aaadd2fbf0@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: bpf: lru: Fix unintended eviction when updating lru hash maps
Date: Wed, 07 Jan 2026 14:14:38 -0800 [thread overview]
Message-ID: <695edace.050a0220.1c677c.0381.GAE@google.com> (raw)
syzbot ci has tested the following series
[v3] bpf: lru: Fix unintended eviction when updating lru hash maps
https://lore.kernel.org/all/20260107151456.72539-1-leon.hwang@linux.dev
* [PATCH bpf-next v3 1/5] bpf: lru: Tidy hash handling in LRU code
* [PATCH bpf-next v3 2/5] bpf: lru: Factor out bpf_lru_node_reset_state helper
* [PATCH bpf-next v3 3/5] bpf: lru: Factor out bpf_lru_move_next_inactive_rotation helper
* [PATCH bpf-next v3 4/5] bpf: lru: Fix unintended eviction when updating lru hash maps
* [PATCH bpf-next v3 5/5] selftests/bpf: Add tests to verify no unintended eviction when updating lru_[percpu_,]hash maps
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/887ab165-3ba2-4319-a149-b620e5250ed5
***
kernel build error
tree: bpf-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base: a069190b590e108223cd841a1c2d0bfb92230ecc
arch: amd64
compiler: Debian clang version 21.1.8 (++20251202083448+f68f64eb8130-1~exp1~20251202083504.46), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/55140e3d-5909-40ea-81ee-75ba1f1d215d/config
kernel/bpf/hashtab.c:1230:24: error: too many arguments to function call, expected 4, have 5
***
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.
The email will later be sent to:
[andrii@kernel.org ast@kernel.org bpf@vger.kernel.org daniel@iogearbox.net davem@davemloft.net eddyz87@gmail.com haoluo@google.com john.fastabend@gmail.com jolsa@kernel.org kernel-patches-bot@fb.com kpsingh@kernel.org leon.hwang@linux.dev linux-kernel@vger.kernel.org linux-kselftest@vger.kernel.org martin.lau@linux.dev sdf@fomichev.me shuah@kernel.org skb99@linux.ibm.com song@kernel.org yonghong.song@linux.dev]
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-01-07 22:14 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=695edace.050a0220.1c677c.0381.GAE@google.com \
--to=syzbot+ci5443f6aaadd2fbf0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox