From: syzbot <syzbot+7ea0b96c4ddb49fd1a70@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [ocfs2?] KMSAN: uninit-value in _find_next_bit
Date: Sun, 23 Mar 2025 18:39:00 -0700 [thread overview]
Message-ID: <67e0b7b4.050a0220.a7ebc.0009.GAE@google.com> (raw)
In-Reply-To: <67ddd191.050a0220.25ae54.006a.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: [syzbot] [ocfs2?] KMSAN: uninit-value in _find_next_bit
Author: lizhi.xu@windriver.com
#syz test
diff --git a/fs/ocfs2/quota_local.c b/fs/ocfs2/quota_local.c
index 2956d888c131..1969772729eb 100644
--- a/fs/ocfs2/quota_local.c
+++ b/fs/ocfs2/quota_local.c
@@ -309,6 +309,8 @@ static int ocfs2_add_recovery_chunk(struct super_block *sb,
}
memcpy(rc->rc_bitmap, dchunk->dqc_bitmap,
(ol_chunk_entries(sb) + 7) >> 3);
+ int bit;
+ for_each_set_bit(bit, rc->rc_bitmap, ol_chunk_entries(sb));
list_add_tail(&rc->rc_list, head);
return 0;
}
next prev parent reply other threads:[~2025-03-24 1:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 20:52 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
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 [this message]
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
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=67e0b7b4.050a0220.a7ebc.0009.GAE@google.com \
--to=syzbot+7ea0b96c4ddb49fd1a70@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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