From: syzbot ci <syzbot+ci4923b488a39b1ae5@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: vfs: replace ints with enum component_type for LAST_XXX
Date: Tue, 31 Mar 2026 16:56:52 -0700 [thread overview]
Message-ID: <69cc5f44.a70a0220.97f31.02a5.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] vfs: replace ints with enum component_type for LAST_XXX
https://lore.kernel.org/all/20260331173726.3517440-1-jkoolstra@xs4all.nl
* [PATCH] vfs: replace ints with enum component_type for LAST_XXX
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/3feaee07-20f8-476a-aca8-283c9782b038
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: d0c3bcd5b8976159d835a897254048e078f447e6
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/923b0f49-bd29-4473-ac86-9a3d42aea014/config
fs/smb/server/vfs.c:71:23: error: incompatible pointer types passing 'int *' to parameter of type 'enum component_type *' [-Werror,-Wincompatible-pointer-types]
fs/smb/server/vfs.c:76:23: error: use of undeclared identifier 'LAST_NORM'
fs/smb/server/vfs.c:681:32: error: incompatible pointer types passing 'int *' to parameter of type 'enum component_type *' [-Werror,-Wincompatible-pointer-types]
***
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.
To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).
The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.
The email will later be sent to:
[amir73il@gmail.com brauner@kernel.org gregkh@linuxfoundation.org jack@suse.cz jkoolstra@xs4all.nl jlayton@kernel.org linkinjeon@kernel.org linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org mjguzik@gmail.com neil@brown.name viro@zeniv.linux.org.uk]
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-31 23:56 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=69cc5f44.a70a0220.97f31.02a5.GAE@google.com \
--to=syzbot+ci4923b488a39b1ae5@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