From: syzbot <syzbot+35257a2200785ea628f5@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu
Subject: [syzbot] [ext4?] KCSAN: data-race in generic_buffers_fsync_noflush / writeback_single_inode (3)
Date: Fri, 02 Aug 2024 00:50:23 -0700 [thread overview]
Message-ID: <000000000000652bb9061eae94a2@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 183d46ff422e Merge tag 'net-6.11-rc2' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1275c375980000
kernel config: https://syzkaller.appspot.com/x/.config?x=d16924117a4f7e9
dashboard link: https://syzkaller.appspot.com/bug?extid=35257a2200785ea628f5
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1a0d5d40de3d/disk-183d46ff.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/aaf4a529fd3b/vmlinux-183d46ff.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9e92264424f5/bzImage-183d46ff.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+35257a2200785ea628f5@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in generic_buffers_fsync_noflush / writeback_single_inode
write to 0xffff88810692fca0 of 8 bytes by task 3596 on cpu 1:
writeback_single_inode+0x10e/0x4a0 fs/fs-writeback.c:1769
sync_inode_metadata+0x5c/0x90 fs/fs-writeback.c:2842
generic_buffers_fsync_noflush+0xe4/0x130 fs/buffer.c:610
ext4_fsync_nojournal fs/ext4/fsync.c:88 [inline]
ext4_sync_file+0x20b/0x6c0 fs/ext4/fsync.c:151
vfs_fsync_range+0x122/0x140 fs/sync.c:188
generic_write_sync include/linux/fs.h:2816 [inline]
ext4_buffered_write_iter+0x338/0x380 fs/ext4/file.c:305
ext4_file_write_iter+0x29f/0xe30
iter_file_splice_write+0x5e6/0x970 fs/splice.c:743
do_splice_from fs/splice.c:941 [inline]
direct_splice_actor+0x16c/0x2c0 fs/splice.c:1164
splice_direct_to_actor+0x305/0x670 fs/splice.c:1108
do_splice_direct_actor fs/splice.c:1207 [inline]
do_splice_direct+0xd7/0x150 fs/splice.c:1233
do_sendfile+0x3ab/0x950 fs/read_write.c:1295
__do_sys_sendfile64 fs/read_write.c:1362 [inline]
__se_sys_sendfile64 fs/read_write.c:1348 [inline]
__x64_sys_sendfile64+0x110/0x150 fs/read_write.c:1348
x64_sys_call+0xfc3/0x2e00 arch/x86/include/generated/asm/syscalls_64.h:41
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
read to 0xffff88810692fca0 of 8 bytes by task 3592 on cpu 0:
generic_buffers_fsync_noflush+0x89/0x130 fs/buffer.c:605
ext4_fsync_nojournal fs/ext4/fsync.c:88 [inline]
ext4_sync_file+0x20b/0x6c0 fs/ext4/fsync.c:151
vfs_fsync_range+0x122/0x140 fs/sync.c:188
generic_write_sync include/linux/fs.h:2816 [inline]
ext4_buffered_write_iter+0x338/0x380 fs/ext4/file.c:305
ext4_file_write_iter+0x29f/0xe30
iter_file_splice_write+0x5e6/0x970 fs/splice.c:743
do_splice_from fs/splice.c:941 [inline]
direct_splice_actor+0x16c/0x2c0 fs/splice.c:1164
splice_direct_to_actor+0x305/0x670 fs/splice.c:1108
do_splice_direct_actor fs/splice.c:1207 [inline]
do_splice_direct+0xd7/0x150 fs/splice.c:1233
do_sendfile+0x3ab/0x950 fs/read_write.c:1295
__do_sys_sendfile64 fs/read_write.c:1362 [inline]
__se_sys_sendfile64 fs/read_write.c:1348 [inline]
__x64_sys_sendfile64+0x110/0x150 fs/read_write.c:1348
x64_sys_call+0xfc3/0x2e00 arch/x86/include/generated/asm/syscalls_64.h:41
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
value changed: 0x0000000000000005 -> 0x0000000000000080
Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 3592 Comm: syz.3.57 Not tainted 6.11.0-rc1-syzkaller-00151-g183d46ff422e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
==================================================================
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
reply other threads:[~2024-08-02 7:50 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=000000000000652bb9061eae94a2@google.com \
--to=syzbot+35257a2200785ea628f5@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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.