* [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_alloc_sectors_start_trans (2)
@ 2025-04-16 17:47 syzbot
2025-05-17 23:36 ` syzbot
2025-07-23 10:59 ` Forwarded: syzbot
0 siblings, 2 replies; 3+ messages in thread
From: syzbot @ 2025-04-16 17:47 UTC (permalink / raw)
To: kent.overstreet, linux-bcachefs, linux-kernel, syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: 1a1d569a75f3 Merge tag 'edac_urgent_for_v6.15_rc3' of git:..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=157c6470580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e30b69a28cc940e1
dashboard link: https://syzkaller.appspot.com/bug?extid=2caec1f3fc52004d4f3c
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/e7fecf1a4718/disk-1a1d569a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7823b994817c/vmlinux-1a1d569a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7ce169c73b39/bzImage-1a1d569a.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2caec1f3fc52004d4f3c@syzkaller.appspotmail.com
=====================================================
BUG: KMSAN: uninit-value in __writepoint_find include/linux/rcupdate.h:-1 [inline]
BUG: KMSAN: uninit-value in writepoint_find fs/bcachefs/alloc_foreground.c:1248 [inline]
BUG: KMSAN: uninit-value in bch2_alloc_sectors_start_trans+0x44a/0x32d0 fs/bcachefs/alloc_foreground.c:1348
__writepoint_find include/linux/rcupdate.h:-1 [inline]
writepoint_find fs/bcachefs/alloc_foreground.c:1248 [inline]
bch2_alloc_sectors_start_trans+0x44a/0x32d0 fs/bcachefs/alloc_foreground.c:1348
__bch2_write+0x7bd/0x6a10 fs/bcachefs/io_write.c:1494
bch2_write+0xdfe/0x1b30 fs/bcachefs/io_write.c:1681
closure_queue include/linux/closure.h:270 [inline]
closure_call include/linux/closure.h:432 [inline]
bch2_writepage_do_io fs/bcachefs/fs-io-buffered.c:494 [inline]
bch2_writepages+0x24a/0x3c0 fs/bcachefs/fs-io-buffered.c:677
do_writepages+0x427/0xc30 mm/page-writeback.c:2656
__writeback_single_inode+0x103/0x1290 fs/fs-writeback.c:1680
writeback_sb_inodes+0xac4/0x1c90 fs/fs-writeback.c:1976
wb_writeback+0x4df/0xcb0 fs/fs-writeback.c:2156
wb_do_writeback fs/fs-writeback.c:2303 [inline]
wb_workfn+0x40b/0x1970 fs/fs-writeback.c:2343
process_one_work kernel/workqueue.c:3238 [inline]
process_scheduled_works+0xc1d/0x1e80 kernel/workqueue.c:3319
worker_thread+0xea3/0x1500 kernel/workqueue.c:3400
kthread+0x6ce/0xf10 kernel/kthread.c:464
ret_from_fork+0x6d/0x90 arch/x86/kernel/process.c:153
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
Uninit was stored to memory at:
bch2_writepage_io_alloc fs/bcachefs/fs-io-buffered.c:522 [inline]
__bch2_writepage+0x3754/0x3ab0 fs/bcachefs/fs-io-buffered.c:644
write_cache_pages+0xc9/0x280 mm/page-writeback.c:2613
bch2_writepages+0x11f/0x3c0 fs/bcachefs/fs-io-buffered.c:675
do_writepages+0x427/0xc30 mm/page-writeback.c:2656
__writeback_single_inode+0x103/0x1290 fs/fs-writeback.c:1680
writeback_sb_inodes+0xac4/0x1c90 fs/fs-writeback.c:1976
wb_writeback+0x4df/0xcb0 fs/fs-writeback.c:2156
wb_do_writeback fs/fs-writeback.c:2303 [inline]
wb_workfn+0x40b/0x1970 fs/fs-writeback.c:2343
process_one_work kernel/workqueue.c:3238 [inline]
process_scheduled_works+0xc1d/0x1e80 kernel/workqueue.c:3319
worker_thread+0xea3/0x1500 kernel/workqueue.c:3400
kthread+0x6ce/0xf10 kernel/kthread.c:464
ret_from_fork+0x6d/0x90 arch/x86/kernel/process.c:153
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
Uninit was created at:
slab_post_alloc_hook mm/slub.c:4157 [inline]
slab_alloc_node mm/slub.c:4200 [inline]
kmem_cache_alloc_lru_noprof+0x92d/0xe30 mm/slub.c:4219
__bch2_new_inode+0x98/0x450 fs/bcachefs/fs.c:438
__bch2_create+0x284/0x1700 fs/bcachefs/fs.c:541
bch2_mknod fs/bcachefs/fs.c:728 [inline]
bch2_create+0xc0/0x1d0 fs/bcachefs/fs.c:742
lookup_open fs/namei.c:3666 [inline]
open_last_lookups fs/namei.c:3765 [inline]
path_openat+0x2efe/0x6280 fs/namei.c:4001
do_filp_open+0x26b/0x610 fs/namei.c:4031
do_sys_openat2+0x1ca/0x300 fs/open.c:1429
do_sys_open fs/open.c:1444 [inline]
__do_sys_openat fs/open.c:1460 [inline]
__se_sys_openat fs/open.c:1455 [inline]
__x64_sys_openat+0x2a1/0x310 fs/open.c:1455
x64_sys_call+0x1fe/0x3c80 arch/x86/include/generated/asm/syscalls_64.h:258
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xcd/0x1e0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
CPU: 1 UID: 0 PID: 3648 Comm: kworker/u8:11 Not tainted 6.15.0-rc2-syzkaller-00042-g1a1d569a75f3 #0 PREEMPT(undef)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: writeback wb_workfn (flush-bcachefs-66)
=====================================================
---
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_alloc_sectors_start_trans (2)
2025-04-16 17:47 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_alloc_sectors_start_trans (2) syzbot
@ 2025-05-17 23:36 ` syzbot
2025-07-23 10:59 ` Forwarded: syzbot
1 sibling, 0 replies; 3+ messages in thread
From: syzbot @ 2025-05-17 23:36 UTC (permalink / raw)
To: kent.overstreet, linux-bcachefs, linux-kernel, syzkaller-bugs
syzbot has found a reproducer for the following issue on:
HEAD commit: 172a9d94339c Merge tag '6.15-rc6-smb3-client-fixes' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=144e62d4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=56e29fa09e87dea7
dashboard link: https://syzkaller.appspot.com/bug?extid=2caec1f3fc52004d4f3c
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15114ef4580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/da9615d2ee0b/disk-172a9d94.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/997b6c928374/vmlinux-172a9d94.xz
kernel image: https://storage.googleapis.com/syzbot-assets/30f01bdce820/bzImage-172a9d94.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/eb7c6f2d77bd/mount_5.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2caec1f3fc52004d4f3c@syzkaller.appspotmail.com
=====================================================
BUG: KMSAN: uninit-value in __writepoint_find fs/bcachefs/alloc_foreground.c:1171 [inline]
BUG: KMSAN: uninit-value in writepoint_find fs/bcachefs/alloc_foreground.c:1248 [inline]
BUG: KMSAN: uninit-value in bch2_alloc_sectors_start_trans+0x4d0/0x3630 fs/bcachefs/alloc_foreground.c:1348
__writepoint_find fs/bcachefs/alloc_foreground.c:1171 [inline]
writepoint_find fs/bcachefs/alloc_foreground.c:1248 [inline]
bch2_alloc_sectors_start_trans+0x4d0/0x3630 fs/bcachefs/alloc_foreground.c:1348
__bch2_write+0x802/0x6bf0 fs/bcachefs/io_write.c:1515
bch2_write+0xe9f/0x1690 fs/bcachefs/io_write.c:1702
closure_queue include/linux/closure.h:270 [inline]
closure_call include/linux/closure.h:432 [inline]
bch2_writepage_do_io fs/bcachefs/fs-io-buffered.c:494 [inline]
bch2_writepages+0x22d/0x430 fs/bcachefs/fs-io-buffered.c:677
do_writepages+0x448/0xcb0 mm/page-writeback.c:2656
__writeback_single_inode+0x101/0x1190 fs/fs-writeback.c:1680
writeback_sb_inodes+0xaa9/0x1c90 fs/fs-writeback.c:1976
wb_writeback+0x4ce/0xc00 fs/fs-writeback.c:2156
wb_do_writeback fs/fs-writeback.c:2303 [inline]
wb_workfn+0x397/0x1910 fs/fs-writeback.c:2343
process_one_work kernel/workqueue.c:3238 [inline]
process_scheduled_works+0xb97/0x1d90 kernel/workqueue.c:3319
worker_thread+0xedf/0x1590 kernel/workqueue.c:3400
kthread+0xd59/0xf00 kernel/kthread.c:464
ret_from_fork+0x6e/0x90 arch/x86/kernel/process.c:153
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
Uninit was stored to memory at:
bch2_writepage_io_alloc fs/bcachefs/fs-io-buffered.c:522 [inline]
__bch2_writepage+0x2b49/0x3c70 fs/bcachefs/fs-io-buffered.c:644
write_cache_pages+0xc8/0x270 mm/page-writeback.c:2613
bch2_writepages+0x121/0x430 fs/bcachefs/fs-io-buffered.c:675
do_writepages+0x448/0xcb0 mm/page-writeback.c:2656
__writeback_single_inode+0x101/0x1190 fs/fs-writeback.c:1680
writeback_sb_inodes+0xaa9/0x1c90 fs/fs-writeback.c:1976
wb_writeback+0x4ce/0xc00 fs/fs-writeback.c:2156
wb_do_writeback fs/fs-writeback.c:2303 [inline]
wb_workfn+0x397/0x1910 fs/fs-writeback.c:2343
process_one_work kernel/workqueue.c:3238 [inline]
process_scheduled_works+0xb97/0x1d90 kernel/workqueue.c:3319
worker_thread+0xedf/0x1590 kernel/workqueue.c:3400
kthread+0xd59/0xf00 kernel/kthread.c:464
ret_from_fork+0x6e/0x90 arch/x86/kernel/process.c:153
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
Uninit was created at:
slab_post_alloc_hook mm/slub.c:4153 [inline]
slab_alloc_node mm/slub.c:4196 [inline]
kmem_cache_alloc_lru_noprof+0x822/0xed0 mm/slub.c:4215
__bch2_new_inode+0x9b/0x4b0 fs/bcachefs/fs.c:457
bch2_new_inode fs/bcachefs/fs.c:483 [inline]
bch2_inode_hash_init_insert+0x82/0x3c0 fs/bcachefs/fs.c:503
bch2_vfs_inode_get+0x565/0x710 fs/bcachefs/fs.c:526
bch2_fs_get_tree+0x1dde/0x2820 fs/bcachefs/fs.c:2576
vfs_get_tree+0xb0/0x5c0 fs/super.c:1759
do_new_mount+0x738/0x1610 fs/namespace.c:3881
path_mount+0x6db/0x1e90 fs/namespace.c:4208
do_mount fs/namespace.c:4221 [inline]
__do_sys_mount fs/namespace.c:4432 [inline]
__se_sys_mount+0x6eb/0x7d0 fs/namespace.c:4409
__x64_sys_mount+0xe4/0x150 fs/namespace.c:4409
x64_sys_call+0xfa7/0x3db0 arch/x86/include/generated/asm/syscalls_64.h:166
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd9/0x1b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
CPU: 1 UID: 0 PID: 5972 Comm: kworker/u8:4 Not tainted 6.15.0-rc6-syzkaller-00278-g172a9d94339c #0 PREEMPT(undef)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: writeback wb_workfn (flush-bcachefs-17)
=====================================================
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Forwarded:
2025-04-16 17:47 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_alloc_sectors_start_trans (2) syzbot
2025-05-17 23:36 ` syzbot
@ 2025-07-23 10:59 ` syzbot
1 sibling, 0 replies; 3+ messages in thread
From: syzbot @ 2025-07-23 10:59 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Add missing ei_last_dirtied update
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-07-23 10:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-04-16 17:47 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_alloc_sectors_start_trans (2) syzbot
2025-05-17 23:36 ` syzbot
2025-07-23 10:59 ` Forwarded: syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox