From: syzbot ci <syzbot+ci6479556fa4e328b6@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: fs: Fix missed inode write during fsync
Date: Thu, 02 Jul 2026 13:31:54 -0700 [thread overview]
Message-ID: <6a46caba.7b9523b0.16a4a.0003.GAE@google.com> (raw)
syzbot ci has tested the following series
[v3] fs: Fix missed inode write during fsync
https://lore.kernel.org/all/20260702175436.12226-1-jack@suse.cz
* [PATCH v3 01/19] affs: Drop support for metadata bh tracking
* [PATCH v3 02/19] fs: Fix possible UAF in mark_buffer_write_io_error()
* [PATCH v3 03/19] fs: Fix missed inode writeback when racing with __writeback_single_inode
* [PATCH v3 04/19] ext4: Allocate mapping_metadata_bhs struct on demand
* [PATCH v3 05/19] ext2: Drop __ext2_write_inode()
* [PATCH v3 06/19] ext2: Avoid unnecessary inode buffer writeback for sync(2)
* [PATCH v3 07/19] fs: Provide way for filesystem to wait for metadata writeback
* [PATCH v3 08/19] ext2: Fix data integrity writeout issues
* [PATCH v3 09/19] udf: Fix data integrity writeout issues
* [PATCH v3 10/19] udf: Use sync_inode_metadata() to writeout IS_SYNC inode
* [PATCH v3 11/19] udf: Write all metadata for IS_SYNC inodes
* [PATCH v3 12/19] udf: Fold udf_update_inode() into udf_write_inode()
* [PATCH v3 13/19] bfs: Fix data integrity writeout issues
* [PATCH v3 14/19] minix: Fix data integrity writeout issues
* [PATCH v3 15/19] ext4: Fix data integrity writeout issues in nojournal mode
* [PATCH v3 16/19] fat: Fix missed inode writeback during fsync(2)
* [PATCH v3 17/19] fat: Remove some superfluous sync_dirty_buffer() calls
* [PATCH v3 18/19] fat: Replace fat_sync_inode() with sync_inode_metadata()
* [PATCH v3 19/19] vfs: Remove mmb_fsync()
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/a71b0842-80ca-4520-bf44-525b2ea88c3f
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 4a50a141f05a8d1737661b19ee22ff8455b94409
arch: amd64
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
config: https://ci.syzbot.org/builds/44a56ebd-5735-4ac4-8072-f7df3748e13e/config
fs/bfs/inode.c:180:43: error: no member named 'ino' in 'struct inode'
***
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:
[aivazian.tigran@gmail.com brauner@kernel.org dsterba@suse.com hirofumi@mail.parknet.co.jp jack@suse.cz linux-ext4@vger.kernel.org linux-fsdevel@vger.kernel.org sashiko-bot@kernel.org tytso@mit.edu]
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-07-02 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 20:31 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-16 21:31 [moderation/CI] Re: fs: Fix missed inode write during fsync syzbot ci
2026-05-11 19:40 syzbot ci
2026-05-11 20:46 ` Aleksandr Nogikh
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=6a46caba.7b9523b0.16a4a.0003.GAE@google.com \
--to=syzbot+ci6479556fa4e328b6@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