From: syzbot <syzbot+7ea0b96c4ddb49fd1a70@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] KMSAN: uninit-value in _find_next_bit
Date: Sat, 22 Mar 2025 02:05:03 -0700 [thread overview]
Message-ID: <67de7d3f.050a0220.31a16b.002d.GAE@google.com> (raw)
In-Reply-To: <tencent_FFC5C6E792E24668C997EEDB6ED34CA52706@qq.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KMSAN: uninit-value in _find_next_bit
ocfs2: Finishing quota recovery on device (7,0) for slot 0
ents: 3990, sb: ffff888042873800, chunk: 0, blksize: 512, rcb: ffff88804b966800, offset: -1, ocfs2_recover_local_quota_file
=====================================================
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:493 [inline]
ocfs2_finish_quota_recovery+0xcc4/0x3fd0 fs/ocfs2/quota_local.c:646
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/0x1450 fs/ocfs2/quota_local.c:363
ocfs2_local_read_info+0x139e/0x2c10 fs/ocfs2/quota_local.c:758
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: 1 UID: 0 PID: 6462 Comm: kworker/u8:0 Not tainted 6.14.0-rc7-syzkaller-g88d324e69ea9-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: ocfs2_wq ocfs2_complete_recovery
=====================================================
Tested on:
commit: 88d324e6 Merge tag 'spi-fix-v6.14-rc7' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13b095e4580000
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
patch: https://syzkaller.appspot.com/x/patch.diff?x=13d9043f980000
next prev parent reply other threads:[~2025-03-22 9:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 20:52 [syzbot] [ocfs2?] KMSAN: uninit-value in _find_next_bit syzbot
2025-03-22 1:40 ` Edward Adam Davis
2025-03-22 6:02 ` syzbot
2025-03-22 8:41 ` Edward Adam Davis
2025-03-22 9:05 ` syzbot [this message]
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
2026-04-17 10:12 ` Forwarded: [PATCH] ocfs2: zero-initialize quota recovery bitmap allocation syzbot
2026-04-17 16:21 ` Forwarded: Re: [syzbot] KMSAN: uninit-value in ocfs2_recover_local_quota_file syzbot
[not found] <20250324010140.2046646-1-lizhi.xu@windriver.com>
2025-03-24 1:21 ` [syzbot] [ocfs2?] KMSAN: uninit-value in _find_next_bit 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
[not found] <20260417101223.2490735-1-tristmd@gmail.com>
2026-04-17 12:37 ` syzbot
[not found] <177644287136.3789634.17252147648817406714@talencesecurity.com>
2026-04-17 19:43 ` 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=67de7d3f.050a0220.31a16b.002d.GAE@google.com \
--to=syzbot+7ea0b96c4ddb49fd1a70@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.