From: syzbot ci <syzbot+cib6966372cefae766@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, 16 Jul 2026 14:31:12 -0700 [thread overview]
Message-ID: <6a594da0.42649fcc.a68e.05cd.GAE@google.com> (raw)
syzbot ci has tested the following series
[v4] fs: Fix missed inode write during fsync
https://lore.kernel.org/all/20260716145359.28639-1-jack@suse.cz
* [PATCH v4 01/21] affs: Drop support for metadata bh tracking
* [PATCH v4 02/21] fs: Fix possible UAF in mark_buffer_write_io_error()
* [PATCH v4 03/21] fs: Fix missed inode writeback when racing with __writeback_single_inode
* [PATCH v4 04/21] ext4: Allocate mapping_metadata_bhs struct on demand
* [PATCH v4 05/21] fs: Provide way for filesystem to wait for metadata writeback
* [PATCH v4 06/21] ext2: Fix lost inode updates for IS_SYNC inodes
* [PATCH v4 07/21] ext2: Drop __ext2_write_inode()
* [PATCH v4 08/21] ext2: Avoid unnecessary inode buffer writeback for sync(2)
* [PATCH v4 09/21] ext2: Fix data integrity writeout issues
* [PATCH v4 10/21] udf: Fix data integrity writeout issues
* [PATCH v4 11/21] udf: Use sync_inode_metadata() to writeout IS_SYNC inode
* [PATCH v4 12/21] udf: Drop udf_sync_inode()
* [PATCH v4 13/21] udf: Use sync_inode_metadata() in udf_evict_inode()
* [PATCH v4 14/21] udf: Fold udf_update_inode() into udf_write_inode()
* [PATCH v4 15/21] bfs: Fix data integrity writeout issues
* [PATCH v4 16/21] minix: Fix data integrity writeout issues
* [PATCH v4 17/21] ext4: Fix data integrity writeout issues in nojournal mode
* [PATCH v4 18/21] fat: Fix missed inode writeback during fsync(2)
* [PATCH v4 19/21] fat: Remove some superfluous sync_dirty_buffer() calls
* [PATCH v4 20/21] fat: Replace fat_sync_inode() with sync_inode_metadata()
* [PATCH v4 21/21] vfs: Remove mmb_fsync()
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/e6aa6f56-8c07-45cd-b1f0-7496a7e04c37
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 37e2f878a7a660a216cc7a60459995fefd150f25
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/2ee33f91-1593-4a29-b326-61478d582a3c/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 stable@vger.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-16 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 21:31 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-02 20: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=6a594da0.42649fcc.a68e.05cd.GAE@google.com \
--to=syzbot+cib6966372cefae766@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.