From: syzbot <syzbot+7ea0b96c4ddb49fd1a70@syzkaller.appspotmail.com>
To: jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
linux-kernel@vger.kernel.org, mark@fasheh.com,
ocfs2-devel@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [ocfs2?] KMSAN: uninit-value in _find_next_bit
Date: Fri, 21 Mar 2025 13:52:33 -0700 [thread overview]
Message-ID: <67ddd191.050a0220.25ae54.006a.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 76b6905c11fd Merge tag 'mm-hotfixes-stable-2025-03-17-20-0..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=16e3c5e4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1d4644c4063c5098
dashboard link: https://syzkaller.appspot.com/bug?extid=7ea0b96c4ddb49fd1a70
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10060a78580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=137eb19b980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/65bb985940e1/disk-76b6905c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0f4133d60a27/vmlinux-76b6905c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0ca5769b6e70/bzImage-76b6905c.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/d3375a361225/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=108c9068580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7ea0b96c4ddb49fd1a70@syzkaller.appspotmail.com
BUG: KMSAN: uninit-value in _find_next_bit+0x11c/0x130 lib/find_bit.c:145
_find_next_bit+0x11c/0x130 lib/find_bit.c:145
find_next_bit include/linux/find.h:69 [inline]
ocfs2_recover_local_quota_file fs/ocfs2/quota_local.c:488 [inline]
ocfs2_finish_quota_recovery+0xc4f/0x3ea0 fs/ocfs2/quota_local.c:641
ocfs2_complete_recovery+0x229f/0x38a0 fs/ocfs2/journal.c:1357
process_one_work kernel/workqueue.c:3238 [inline]
process_scheduled_works+0xc1a/0x1e80 kernel/workqueue.c:3319
worker_thread+0xea7/0x14f0 kernel/workqueue.c:3400
kthread+0x6b9/0xef0 kernel/kthread.c:464
ret_from_fork+0x6d/0x90 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
Uninit was created at:
slab_post_alloc_hook mm/slub.c:4121 [inline]
slab_alloc_node mm/slub.c:4164 [inline]
__do_kmalloc_node mm/slub.c:4293 [inline]
__kmalloc_noprof+0x923/0x1230 mm/slub.c:4306
kmalloc_noprof include/linux/slab.h:905 [inline]
ocfs2_add_recovery_chunk fs/ocfs2/quota_local.c:305 [inline]
ocfs2_recovery_load_quota+0x415/0x1150 fs/ocfs2/quota_local.c:360
ocfs2_local_read_info+0x139e/0x2c10 fs/ocfs2/quota_local.c:753
dquot_load_quota_sb+0xa35/0xdc0 fs/quota/dquot.c:2459
dquot_load_quota_inode+0x662/0x9f0 fs/quota/dquot.c:2496
ocfs2_enable_quotas+0x1d4/0x6e0 fs/ocfs2/super.c:930
ocfs2_fill_super+0xa6b7/0xb550 fs/ocfs2/super.c:1140
get_tree_bdev_flags+0x6ec/0x910 fs/super.c:1636
get_tree_bdev+0x37/0x50 fs/super.c:1659
ocfs2_get_tree+0x34/0x40 fs/ocfs2/super.c:1184
vfs_get_tree+0xb1/0x5a0 fs/super.c:1814
do_new_mount+0x71f/0x15e0 fs/namespace.c:3560
path_mount+0x742/0x1f10 fs/namespace.c:3887
do_mount fs/namespace.c:3900 [inline]
__do_sys_mount fs/namespace.c:4111 [inline]
__se_sys_mount+0x71f/0x800 fs/namespace.c:4088
__x64_sys_mount+0xe4/0x150 fs/namespace.c:4088
x64_sys_call+0x39bf/0x3c30 arch/x86/include/generated/asm/syscalls_64.h:166
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: 0 UID: 0 PID: 3555 Comm: kworker/u8:11 Not tainted 6.14.0-rc7-syzkaller-00067-g76b6905c11fd #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: ocfs2_wq ocfs2_complete_recovery
=====================================================
---
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
next reply other threads:[~2025-03-21 20:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 20:52 syzbot [this message]
2025-03-22 1:40 ` [syzbot] [ocfs2?] KMSAN: uninit-value in _find_next_bit Edward Adam Davis
2025-03-22 6:02 ` syzbot
2025-03-22 8:41 ` Edward Adam Davis
2025-03-22 9:05 ` syzbot
2025-03-23 2:36 ` Edward Adam Davis
2025-03-23 9:52 ` syzbot
2025-03-23 10:17 ` Edward Adam Davis
2025-03-23 10:43 ` syzbot
2025-03-24 1:01 ` [syzbot] " syzbot
2025-03-24 1:39 ` syzbot
2025-03-26 1:09 ` [PATCH] " I Hsin Cheng
2025-03-26 1:23 ` I Hsin Cheng
2025-03-26 1:59 ` syzbot
2025-03-26 2:19 ` I Hsin Cheng
2025-03-26 2:43 ` syzbot
2025-03-26 3:04 ` I Hsin Cheng
2025-03-26 3:58 ` syzbot
2025-03-26 3:20 ` [syzbot] " syzbot
[not found] <20250324010140.2046646-1-lizhi.xu@windriver.com>
2025-03-24 1:21 ` syzbot
[not found] <20250324013855.2122966-1-lizhi.xu@windriver.com>
2025-03-24 2:23 ` syzbot
[not found] <20250326032012.83642-1-richard120310@gmail.com>
2025-03-26 4:15 ` syzbot
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=67ddd191.050a0220.25ae54.006a.GAE@google.com \
--to=syzbot+7ea0b96c4ddb49fd1a70@syzkaller.appspotmail.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@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