From: syzbot ci <syzbot+ci4f7e07ad5d3fa724@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: bpf: Avoid locks in bpf_timer and bpf_wq
Date: Wed, 07 Jan 2026 15:45:41 -0800 [thread overview]
Message-ID: <695ef025.050a0220.1c677c.0385.GAE@google.com> (raw)
syzbot ci has tested the following series
[v3] bpf: Avoid locks in bpf_timer and bpf_wq
https://lore.kernel.org/all/20260107-timer_nolock-v3-0-740d3ec3e5f9@meta.com
* [PATCH RFC v3 01/10] bpf: Refactor __bpf_async_set_callback()
* [PATCH RFC v3 02/10] bpf: Factor out timer deletion helper
* [PATCH RFC v3 03/10] bpf: Simplify bpf_timer_cancel()
* [PATCH RFC v3 04/10] bpf: Add lock-free cell for NMI-safe async operations
* [PATCH RFC v3 05/10] bpf: Enable bpf timer and workqueue use in NMI
* [PATCH RFC v3 06/10] bpf: Add verifier support for bpf_timer argument in kfuncs
* [PATCH RFC v3 07/10] bpf: Introduce bpf_timer_cancel_async() kfunc
* [PATCH RFC v3 08/10] selftests/bpf: Refactor timer selftests
* [PATCH RFC v3 09/10] selftests/bpf: Add stress test for timer async cancel
* [PATCH RFC v3 10/10] selftests/bpf: Verify bpf_timer_cancel_async works
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/595c48b9-bc4e-4ede-847d-8f2d847f2dcb
***
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/429abbbb-1b09-420d-ada7-16187822d5b4/config
kernel/bpf/helpers.c:32:10: error: 'mpmc_cell.h' file not found with <angled> include; use "quotes" instead
***
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 eddyz87@gmail.com kafai@meta.com kernel-team@meta.com memxor@gmail.com mykyta.yatsenko5@gmail.com yatsenko@meta.com]
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 23:45 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=695ef025.050a0220.1c677c.0385.GAE@google.com \
--to=syzbot+ci4f7e07ad5d3fa724@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