[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <000000000000b3424a062114aaa3@google.com>
Date: Sun, 01 Sep 2024 13:28:27 -0700
From: syzbot <syzbot+7a2ba6b7b66340cff225@...kaller.appspotmail.com>
To: almaz.alexandrovich@...agon-software.com, linux-kernel@...r.kernel.org,
ntfs3@...ts.linux.dev, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_read_bh
Hello,
syzbot found the following issue on:
HEAD commit: 431c1646e1f8 Linux 6.11-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=137426eb980000
kernel config: https://syzkaller.appspot.com/x/.config?x=35c699864e165c51
dashboard link: https://syzkaller.appspot.com/bug?extid=7a2ba6b7b66340cff225
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/5ab3219cb5e8/disk-431c1646.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/82e6779c1851/vmlinux-431c1646.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d5d4a104ce36/bzImage-431c1646.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7a2ba6b7b66340cff225@...kaller.appspotmail.com
=====================================================
BUG: KMSAN: uninit-value in ntfs_fix_post_read fs/ntfs3/fsntfs.c:180 [inline]
BUG: KMSAN: uninit-value in ntfs_read_bh+0x1eb/0xde0 fs/ntfs3/fsntfs.c:1317
ntfs_fix_post_read fs/ntfs3/fsntfs.c:180 [inline]
ntfs_read_bh+0x1eb/0xde0 fs/ntfs3/fsntfs.c:1317
indx_read+0x44e/0x17b0 fs/ntfs3/index.c:1067
indx_find+0xd12/0x1440 fs/ntfs3/index.c:1181
indx_update_dup+0x607/0xf80 fs/ntfs3/index.c:2666
ni_update_parent+0x12de/0x14b0 fs/ntfs3/frecord.c:3301
ni_write_inode+0x1cf4/0x1de0 fs/ntfs3/frecord.c:3392
ntfs3_write_inode+0x94/0xb0 fs/ntfs3/inode.c:1052
write_inode fs/fs-writeback.c:1497 [inline]
__writeback_single_inode+0x849/0x12c0 fs/fs-writeback.c:1716
writeback_sb_inodes+0xc95/0x1e00 fs/fs-writeback.c:1947
wb_writeback+0x4df/0xea0 fs/fs-writeback.c:2127
wb_do_writeback fs/fs-writeback.c:2274 [inline]
wb_workfn+0x40b/0x1940 fs/fs-writeback.c:2314
process_one_work kernel/workqueue.c:3231 [inline]
process_scheduled_works+0xae0/0x1c40 kernel/workqueue.c:3312
worker_thread+0xea7/0x14d0 kernel/workqueue.c:3389
kthread+0x3e2/0x540 kernel/kthread.c:389
ret_from_fork+0x6d/0x90 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
Uninit was stored to memory at:
ntfs_read_run_nb+0x786/0x1070 fs/ntfs3/fsntfs.c:1252
ntfs_read_bh+0x64/0xde0 fs/ntfs3/fsntfs.c:1313
indx_read+0x44e/0x17b0 fs/ntfs3/index.c:1067
indx_find+0xd12/0x1440 fs/ntfs3/index.c:1181
indx_update_dup+0x607/0xf80 fs/ntfs3/index.c:2666
ni_update_parent+0x12de/0x14b0 fs/ntfs3/frecord.c:3301
ni_write_inode+0x1cf4/0x1de0 fs/ntfs3/frecord.c:3392
ntfs3_write_inode+0x94/0xb0 fs/ntfs3/inode.c:1052
write_inode fs/fs-writeback.c:1497 [inline]
__writeback_single_inode+0x849/0x12c0 fs/fs-writeback.c:1716
writeback_sb_inodes+0xc95/0x1e00 fs/fs-writeback.c:1947
wb_writeback+0x4df/0xea0 fs/fs-writeback.c:2127
wb_do_writeback fs/fs-writeback.c:2274 [inline]
wb_workfn+0x40b/0x1940 fs/fs-writeback.c:2314
process_one_work kernel/workqueue.c:3231 [inline]
process_scheduled_works+0xae0/0x1c40 kernel/workqueue.c:3312
worker_thread+0xea7/0x14d0 kernel/workqueue.c:3389
kthread+0x3e2/0x540 kernel/kthread.c:389
ret_from_fork+0x6d/0x90 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
Uninit was created at:
__alloc_pages_noprof+0x9d6/0xe70 mm/page_alloc.c:4718
alloc_pages_mpol_noprof+0x299/0x990 mm/mempolicy.c:2263
alloc_pages_noprof mm/mempolicy.c:2343 [inline]
folio_alloc_noprof+0x1db/0x310 mm/mempolicy.c:2350
filemap_alloc_folio_noprof+0xa6/0x440 mm/filemap.c:1008
__filemap_get_folio+0xa05/0x14b0 mm/filemap.c:1950
grow_dev_folio fs/buffer.c:1047 [inline]
grow_buffers fs/buffer.c:1113 [inline]
__getblk_slow fs/buffer.c:1139 [inline]
bdev_getblk+0x2c9/0xab0 fs/buffer.c:1441
__getblk include/linux/buffer_head.h:381 [inline]
sb_getblk include/linux/buffer_head.h:387 [inline]
ntfs_get_bh+0x605/0x1190 fs/ntfs3/fsntfs.c:1365
indx_new+0x1bc/0x780 fs/ntfs3/index.c:955
indx_insert_into_root+0x2fd1/0x37d0 fs/ntfs3/index.c:1723
indx_insert_entry+0xe1d/0xee0 fs/ntfs3/index.c:1982
ntfs_create_inode+0x4391/0x4df0 fs/ntfs3/inode.c:1689
ntfs_mkdir+0x56/0x70 fs/ntfs3/namei.c:207
vfs_mkdir+0x4a0/0x780 fs/namei.c:4210
do_mkdirat+0x529/0x810 fs/namei.c:4233
__do_sys_mkdirat fs/namei.c:4248 [inline]
__se_sys_mkdirat fs/namei.c:4246 [inline]
__x64_sys_mkdirat+0xc6/0x120 fs/namei.c:4246
x64_sys_call+0x3a81/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:259
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
CPU: 1 UID: 0 PID: 2918 Comm: kworker/u8:9 Not tainted 6.11.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Workqueue: writeback wb_workfn (flush-7:4)
=====================================================
---
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@...glegroups.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
Powered by blists - more mailing lists