From: syzbot ci <syzbot+cie1fd169c18565fec@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm: convert VM flags from macros to enum
Date: Sat, 11 Oct 2025 02:59:57 -0700 [thread overview]
Message-ID: <68ea2a9d.050a0220.91a22.01cd.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] mm: convert VM flags from macros to enum
https://lore.kernel.org/all/20251011093054.886460-1-ye.liu@linux.dev
* [RFC RFC PATCH] mm: convert VM flags from macros to enum
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/725db1a7-60b8-44dd-b2b7-29c495be3a0f
***
kernel build error
tree: linux-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base: 4a71531471926e3c391665ee9c42f4e0295a4585
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/e439ac1e-2898-4f54-a585-0792f1b2e1c5/config
failed to run ["make" "KERNELVERSION=syzkaller" "KERNELRELEASE=syzkaller" "LOCALVERSION=-syzkaller" "-j" "48" "ARCH=x86_64" "LLVM=1" "bzImage"]: exit status 2
***
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 david@redhat.com liam.howlett@oracle.com linux-kernel@vger.kernel.org linux-mm@kvack.org liuye@kylinos.cn lorenzo.stoakes@oracle.com mhocko@suse.com rppt@kernel.org surenb@google.com vbabka@suse.cz ye.liu@linux.dev]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-10-11 9:59 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=68ea2a9d.050a0220.91a22.01cd.GAE@google.com \
--to=syzbot+cie1fd169c18565fec@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