From: syzbot <syzbot+549710bad9c798e25b15@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [crypto?] KMSAN: uninit-value in __crc32c_le_base (4)
Date: Wed, 23 Apr 2025 08:32:50 -0700 [thread overview]
Message-ID: <68090822.050a0220.dd94f.01f1.GAE@google.com> (raw)
In-Reply-To: <000000000000736bd406151001d7@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: [syzbot] [crypto?] KMSAN: uninit-value in __crc32c_le_base (4)
Author: richard120310@gmail.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 614da38e2f7a
Signed-off-by: I Hsin Cheng <richard120310@gmail.com>
---
fs/bcachefs/btree_io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/bcachefs/btree_io.c b/fs/bcachefs/btree_io.c
index debb0edc3455..dc00c5273ffe 100644
--- a/fs/bcachefs/btree_io.c
+++ b/fs/bcachefs/btree_io.c
@@ -115,7 +115,7 @@ static void *btree_bounce_alloc(struct bch_fs *c, size_t size,
BUG_ON(size > c->opts.btree_node_size);
*used_mempool = false;
- p = kvmalloc(size, __GFP_NOWARN|GFP_NOWAIT);
+ p = kvzalloc(size, __GFP_NOWARN|GFP_NOWAIT);
if (!p) {
*used_mempool = true;
p = mempool_alloc(&c->btree_bounce_pool, GFP_NOFS);
--
2.43.0
next prev parent reply other threads:[~2025-04-23 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 21:52 [syzbot] [crypto?] KMSAN: uninit-value in __crc32c_le_base (4) syzbot
2024-04-03 9:39 ` Herbert Xu
2024-05-09 7:22 ` [syzbot] [btrfs] " syzbot
2024-11-15 15:21 ` [syzbot] Re: KMSAN: uninit-value in __crc32c_le_base syzbot
2025-04-23 15:32 ` syzbot [this message]
2025-04-23 16:37 ` [PATCH] bcachefs: Fix unit-value within btree_bounce_alloc() I Hsin Cheng
2025-04-23 16:45 ` Kent Overstreet
2025-04-25 16:53 ` I Hsin Cheng
2025-04-26 15:03 ` Kent Overstreet
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=68090822.050a0220.dd94f.01f1.GAE@google.com \
--to=syzbot+549710bad9c798e25b15@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