From: syzbot <syzbot+ff8bd63dc02136db5a1a@syzkaller.appspotmail.com>
To: hirofumi@mail.parknet.co.jp, linkinjeon@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
sj1557.seo@samsung.com, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [exfat?] KCSAN: data-race in fat12_ent_put / fat_mirror_bhs (2)
Date: Sat, 12 Sep 2026 07:38:28 -0700 [thread overview]
Message-ID: <6aa563e4.f2639fcc.29487d.0041.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 3026c6e4f223 Merge tag 'slab-for-7.3-rc2' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=117769f9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e3dbeec937af205c
dashboard link: https://syzkaller.appspot.com/bug?extid=ff8bd63dc02136db5a1a
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/31e48aab7540/disk-3026c6e4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4e31dbebfbd9/vmlinux-3026c6e4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cf95aa277f9d/bzImage-3026c6e4.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ff8bd63dc02136db5a1a@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in fat12_ent_put / fat_mirror_bhs
read-write to 0xffff88810c2e3f2a of 1 bytes by task 8373 on cpu 0:
fat12_ent_put+0xc4/0x180 fs/fat/fatent.c:165
fat_ent_write+0x6c/0xe0 fs/fat/fatent.c:422
fat_chain_add+0x170/0x4c0 fs/fat/misc.c:138
fat_add_cluster fs/fat/inode.c:113 [inline]
__fat_get_block fs/fat/inode.c:155 [inline]
fat_get_block+0x468/0x5e0 fs/fat/inode.c:190
__block_write_begin_int+0x400/0xf90 fs/buffer.c:2030
block_write_begin fs/buffer.c:2144 [inline]
cont_write_begin+0x5bf/0x920 fs/buffer.c:2506
fat_write_begin+0x52/0xe0 fs/fat/inode.c:230
generic_perform_write+0x186/0x490 mm/filemap.c:4374
__generic_file_write_iter+0x9e/0x120 mm/filemap.c:4491
generic_file_write_iter+0x77/0x1f0 mm/filemap.c:4517
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x57f/0x9a0 fs/read_write.c:687
ksys_write+0xdc/0x1a0 fs/read_write.c:739
__do_sys_write fs/read_write.c:750 [inline]
__se_sys_write fs/read_write.c:747 [inline]
__x64_sys_write+0x40/0x50 fs/read_write.c:747
x64_sys_call+0x154e/0x2550 arch/x86/include/generated/asm/syscalls_64.h:2
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x112/0x360 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
read to 0xffff88810c2e3e00 of 512 bytes by task 8427 on cpu 1:
fat_mirror_bhs+0x1df/0x330 fs/fat/fatent.c:399
fat_ent_write+0xd0/0xe0 fs/fat/fatent.c:428
fat_chain_add+0x170/0x4c0 fs/fat/misc.c:138
fat_add_cluster fs/fat/inode.c:113 [inline]
__fat_get_block fs/fat/inode.c:155 [inline]
fat_get_block+0x468/0x5e0 fs/fat/inode.c:190
__block_write_begin_int+0x400/0xf90 fs/buffer.c:2030
block_write_begin fs/buffer.c:2144 [inline]
cont_write_begin+0x5bf/0x920 fs/buffer.c:2506
fat_write_begin+0x52/0xe0 fs/fat/inode.c:230
generic_perform_write+0x186/0x490 mm/filemap.c:4374
__generic_file_write_iter+0x9e/0x120 mm/filemap.c:4491
generic_file_write_iter+0x77/0x1f0 mm/filemap.c:4517
__kernel_write_iter+0x30f/0x590 fs/read_write.c:621
dump_emit_page fs/coredump.c:1293 [inline]
dump_user_range+0xa73/0xd00 fs/coredump.c:1367
elf_core_dump+0x21c0/0x2340 fs/binfmt_elf.c:2106
coredump_write+0xafb/0xdd0 fs/coredump.c:1047
do_coredump fs/coredump.c:1126 [inline]
vfs_coredump+0x2762/0x3270 fs/coredump.c:1195
get_signal+0xd33/0xf10 kernel/signal.c:3036
arch_do_signal_or_restart+0x96/0x480 arch/x86/kernel/signal.c:337
__exit_to_user_mode_loop kernel/entry/common.c:66 [inline]
exit_to_user_mode_loop kernel/entry/common.c:101 [inline]
__exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
irqentry_exit_to_user_mode_prepare include/linux/irq-entry-common.h:244 [inline]
irqentry_exit_to_user_mode include/linux/irq-entry-common.h:315 [inline]
irqentry_exit+0x14d/0x610 kernel/entry/common.c:165
exc_general_protection+0x155/0x1e0 arch/x86/kernel/traps.c:914
asm_exc_general_protection+0x26/0x30 arch/x86/include/asm/idtentry.h:589
Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 8427 Comm: syz.4.1138 Not tainted syzkaller #0 PREEMPT(lazy)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
==================================================================
---
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:[~2026-09-12 14:38 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=6aa563e4.f2639fcc.29487d.0041.GAE@google.com \
--to=syzbot+ff8bd63dc02136db5a1a@syzkaller.appspotmail.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=syzkaller-bugs@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
all inboxes | Powered by JetHome®