public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7be88937363ac7ab7bb0@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
	linux-kernel@vger.kernel.org,  ntfs3@lists.linux.dev,
	syzkaller-bugs@googlegroups.com
Subject: [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_iomap_begin
Date: Sun, 22 Feb 2026 03:33:31 -0800	[thread overview]
Message-ID: <699ae98b.050a0220.340abe.0d30.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    d79526b89571 Merge tag 'spi-fix-v7.0-merge-window' of git:..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17c90006580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e9e76fdaa4072fa5
dashboard link: https://syzkaller.appspot.com/bug?extid=7be88937363ac7ab7bb0
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1016255a580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16197c02580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9632d1edcebe/disk-d79526b8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c9f69df31226/vmlinux-d79526b8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/54f77eae730c/bzImage-d79526b8.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/62ad4352d8b0/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7be88937363ac7ab7bb0@syzkaller.appspotmail.com

loop0: detected capacity change from 0 to 4096
ntfs3(loop0): Different NTFS sector size (2048) and media sector size (512).
=====================================================
BUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825
 ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825
 iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110
 iomap_read_folio+0x262/0x750 fs/iomap/buffered-io.c:587
 ntfs_read_folio+0x74a/0x770 fs/ntfs3/inode.c:697
 filemap_read_folio mm/filemap.c:2496 [inline]
 do_read_cache_folio+0x993/0x1470 mm/filemap.c:4096
 do_read_cache_page mm/filemap.c:4162 [inline]
 read_cache_page+0x63/0x1e0 mm/filemap.c:4171
 read_mapping_page include/linux/pagemap.h:1022 [inline]
 inode_read_data+0xb3/0x6b0 fs/ntfs3/inode.c:1116
 ntfs_fill_super+0x6a24/0x7e50 fs/ntfs3/super.c:1549
 get_tree_bdev_flags+0x6e6/0x920 fs/super.c:1694
 get_tree_bdev+0x38/0x50 fs/super.c:1717
 ntfs_fs_get_tree+0x35/0x40 fs/ntfs3/super.c:1788
 vfs_get_tree+0xb3/0x5d0 fs/super.c:1754
 fc_mount fs/namespace.c:1193 [inline]
 do_new_mount_fc fs/namespace.c:3760 [inline]
 do_new_mount+0x885/0x1dd0 fs/namespace.c:3836
 path_mount+0x7a2/0x20b0 fs/namespace.c:4146
 do_mount fs/namespace.c:4159 [inline]
 __do_sys_mount fs/namespace.c:4348 [inline]
 __se_sys_mount+0x704/0x7f0 fs/namespace.c:4325
 __x64_sys_mount+0xe4/0x150 fs/namespace.c:4325
 x64_sys_call+0x39f0/0x3ea0 arch/x86/include/generated/asm/syscalls_64.h:166
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x134/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Local variable lcn created at:
 ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786
 iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110

CPU: 1 UID: 0 PID: 6051 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/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 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.

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-02-22 11:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-22 11:33 syzbot [this message]
2026-02-23  7:23 ` [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_iomap_begin Edward Adam Davis
2026-02-23  7:53   ` syzbot
2026-02-23  8:01 ` [PATCH] fs/ntfs3: prevent uninitialized lcn caused by zero len Edward Adam Davis
2026-03-02 13:51   ` Konstantin Komarov

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=699ae98b.050a0220.340abe.0d30.GAE@google.com \
    --to=syzbot+7be88937363ac7ab7bb0@syzkaller.appspotmail.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --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