From: syzbot ci <syzbot+ci72a5022aa3627ac9@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm: zone lock tracepoint instrumentation
Date: Fri, 27 Feb 2026 03:31:26 -0800 [thread overview]
Message-ID: <69a1808e.050a0220.3a55be.001b.GAE@google.com> (raw)
syzbot ci has tested the following series
[v3] mm: zone lock tracepoint instrumentation
https://lore.kernel.org/all/cover.1772129168.git.d@ilvokhin.com
* [PATCH v3 1/5] mm: introduce zone lock wrappers
* [PATCH v3 2/5] mm: convert zone lock users to wrappers
* [PATCH v3 3/5] mm: convert compaction to zone lock wrappers
* [PATCH v3 4/5] mm: rename zone->lock to zone->_lock
* [PATCH v3 5/5] mm: add tracepoints for zone lock
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/cfcd7061-63fb-4da3-abcb-ea888afce613
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 3f4a08e64442340f4807de63e30aef22cc308830
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/f7743631-8ec3-49f9-ad7a-3e99f580cd40/config
kernel/power/snapshot.c:1254:27: error: no member named 'lock' in 'struct zone'
kernel/power/snapshot.c:1287:32: error: no member named 'lock' in 'struct zone'
***
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:
[akpm@linux-foundation.org axelrasmussen@google.com benjamin.cheatham@amd.com d@ilvokhin.com david@kernel.org hannes@cmpxchg.org jackmanb@google.com kernel-team@meta.com liam.howlett@oracle.com linux-cxl@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org linux-trace-kernel@vger.kernel.org lorenzo.stoakes@oracle.com mathieu.desnoyers@efficios.com mhiramat@kernel.org mhocko@suse.com osalvador@suse.de rostedt@goodmis.org rppt@kernel.org shakeel.butt@linux.dev surenb@google.com vbabka@suse.cz weixugc@google.com yuanchu@google.com zhengqi.arch@bytedance.com ziy@nvidia.com]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
next reply other threads:[~2026-02-27 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 11:31 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-11 19:35 [moderation/CI] Re: mm: zone lock tracepoint instrumentation syzbot ci
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=69a1808e.050a0220.3a55be.001b.GAE@google.com \
--to=syzbot+ci72a5022aa3627ac9@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