From: syzbot ci <syzbot+ci813d9da582e3e948@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: Exposing case folding behavior
Date: Mon, 12 Jan 2026 14:14:15 -0800 [thread overview]
Message-ID: <69657237.050a0220.3be5c5.0006.GAE@google.com> (raw)
syzbot ci has tested the following series
[v3] Exposing case folding behavior
https://lore.kernel.org/all/20260112174629.3729358-1-cel@kernel.org
* [PATCH v3 01/16] fs: Add case sensitivity info to file_kattr
* [PATCH v3 02/16] fat: Implement fileattr_get for case sensitivity
* [PATCH v3 03/16] exfat: Implement fileattr_get for case sensitivity
* [PATCH v3 04/16] ntfs3: Implement fileattr_get for case sensitivity
* [PATCH v3 05/16] hfs: Implement fileattr_get for case sensitivity
* [PATCH v3 06/16] hfsplus: Report case sensitivity in fileattr_get
* [PATCH v3 07/16] ext4: Report case sensitivity in fileattr_get
* [PATCH v3 08/16] xfs: Report case sensitivity in fileattr_get
* [PATCH v3 09/16] cifs: Implement fileattr_get for case sensitivity
* [PATCH v3 10/16] nfs: Implement fileattr_get for case sensitivity
* [PATCH v3 11/16] f2fs: Add case sensitivity reporting to fileattr_get
* [PATCH v3 12/16] vboxsf: Implement fileattr_get for case sensitivity
* [PATCH v3 13/16] isofs: Implement fileattr_get for case sensitivity
* [PATCH v3 14/16] nfsd: Report export case-folding via NFSv3 PATHCONF
* [PATCH v3 15/16] nfsd: Implement NFSv4 FATTR4_CASE_INSENSITIVE and FATTR4_CASE_PRESERVING
* [PATCH v3 16/16] ksmbd: Report filesystem case sensitivity via FS_ATTRIBUTE_INFORMATION
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/389a66d5-7460-40b3-9f6b-1cfae867c1c3
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 0f61b1860cc3f52aef9036d7235ed1f017632193
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/5eaf1d58-f83f-46bc-a58a-4fd05cfab461/config
./include/linux/fileattr.h:74:23: error: use of undeclared identifier 'FS_XFLAG_SYNC'
./include/linux/fileattr.h:74:23: error: use of undeclared identifier 'FS_XFLAG_IMMUTABLE'
./include/linux/fileattr.h:74:23: error: use of undeclared identifier 'FS_XFLAG_APPEND'
./include/linux/fileattr.h:74:23: error: use of undeclared identifier 'FS_XFLAG_NODUMP'
./include/linux/fileattr.h:74:23: error: use of undeclared identifier 'FS_XFLAG_NOATIME'
./include/linux/fileattr.h:74:23: error: use of undeclared identifier 'FS_XFLAG_DAX'
./include/linux/fileattr.h:74:23: error: use of undeclared identifier 'FS_XFLAG_PROJINHERIT'
***
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:
[adilger.kernel@dilger.ca almaz.alexandrovich@paragon-software.com anna@kernel.org cel@kernel.org cem@kernel.org chao@kernel.org chuck.lever@oracle.com frank.li@vivo.com glaubitz@physik.fu-berlin.de hansg@kernel.org hirofumi@mail.parknet.co.jp jaegeuk@kernel.org linkinjeon@kernel.org linux-cifs@vger.kernel.org linux-ext4@vger.kernel.org linux-f2fs-devel@lists.sourceforge.net linux-fsdevel@vger.kernel.org linux-nfs@vger.kernel.org linux-xfs@vger.kernel.org pc@manguebit.org ronniesahlberg@gmail.com senozhatsky@chromium.org sfrench@samba.org sj1557.seo@samsung.com slava@dubeyko.com sprasad@microsoft.com trondmy@kernel.org tytso@mit.edu yuezhang.mo@sony.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-01-12 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 22:14 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-14 17:00 [moderation/CI] Re: Exposing case folding behavior syzbot ci
2026-01-16 17:24 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=69657237.050a0220.3be5c5.0006.GAE@google.com \
--to=syzbot+ci813d9da582e3e948@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.