From: syzbot ci <syzbot+cib64ad39f77b6c92e@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: locking: contended_release tracepoint instrumentation
Date: Thu, 19 Mar 2026 05:21:14 -0700 [thread overview]
Message-ID: <69bbea3a.050a0220.3a088d.0012.GAE@google.com> (raw)
syzbot ci has tested the following series
[v3] locking: contended_release tracepoint instrumentation
https://lore.kernel.org/all/cover.1773858853.git.d@ilvokhin.com
* [PATCH v3 1/4] tracing/lock: Remove unnecessary linux/sched.h include
* [PATCH v3 2/4] locking/percpu-rwsem: Extract __percpu_up_read()
* [PATCH v3 3/4] locking: Add contended_release tracepoint to sleepable locks
* [RFC PATCH v3 4/4] locking: Add contended_release tracepoint to spinning locks
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/76d0e02e-59d8-4b47-9e05-ac2b9870fb24
***
kernel build error
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: 39849a55738542a4cdef8394095ccfa98530e250
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/a74474c1-b3a4-4247-a0b6-cf264610d3d7/config
kernel/locking/mutex.c:978:43: error: use of undeclared identifier 'waiter'
***
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:
[arnd@arndb.de boqun@kernel.org cl@gentwo.org d@ilvokhin.com dennis@kernel.org kernel-team@meta.com linux-arch@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org linux-trace-kernel@vger.kernel.org longman@redhat.com mathieu.desnoyers@efficios.com mhiramat@kernel.org mingo@redhat.com peterz@infradead.org rostedt@goodmis.org tj@kernel.org usama.arif@linux.dev will@kernel.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-03-19 12:21 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=69bbea3a.050a0220.3a088d.0012.GAE@google.com \
--to=syzbot+cib64ad39f77b6c92e@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