From: syzbot ci <syzbot+ci4061e751499e87dd@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: Remove FGP_NOFS
Date: Sat, 29 Aug 2026 22:21:42 -0700 [thread overview]
Message-ID: <6a93bde6.4d659fcc.734b4.0035.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] Remove FGP_NOFS
https://lore.kernel.org/all/20260830041901.2668-1-willy@infradead.org
* [PATCH 1/9] mm: Improve memalloc_nofs_save() documentation
* [PATCH 2/9] ext4: Remove uses of FGP_NOFS
* [PATCH 3/9] erofs: Remove redundant FGP_NOFS
* [PATCH 4/9] nfs: Remove redundant FGP_NOFS
* [PATCH 5/9] ntfs: Remove FGP_NOFS from __ntfs_inode_resident_attr_pwrite()
* [PATCH 6/9] ntfs: Remove redundant FGP_NOFS from ntfs_wof_collect_dest()
* [PATCH 7/9] squashfs: Remove use of FGP_NOFS
* [PATCH 8/9] filemap: Remove redundant FGP_NOFS
* [PATCH 9/9] filemap: Remove FGP_NOFS
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/30b4b362-31a6-46cf-a7d0-8df2be654a16
***
kernel build error
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: d2aad7fdcda7ae8a726926f2d6de7fe9e8ee7563
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/0bf0117c-21b3-4384-be5f-29194d5ea5e4/config
fs/f2fs/data.c:3903:40: error: use of undeclared identifier 'FGP_NOFS'
***
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 fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.
Notes:
- The patch will be applied on top of the tested series (as an
incremental fix).
- To test a new version of the whole series, please send it directly
to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.
The email will later be sent to:
[anna@kernel.org chao@kernel.org christian@brauner.io hyc.lee@gmail.com jack@suse.cz linkinjeon@kernel.org linux-erofs@lists.ozlabs.org linux-ext4@vger.kernel.org linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org linux-nfs@vger.kernel.org ntfs@lists.linux.dev phillip@squashfs.org.uk trondmy@kernel.org tytso@mit.edu willy@infradead.org xiang@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-08-30 5: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=6a93bde6.4d659fcc.734b4.0035.GAE@google.com \
--to=syzbot+ci4061e751499e87dd@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