From: Gianfranco Trad <gianf.trad@gmail.com>
To: syzbot <syzbot+2e6fb1f89ce5e13cd02d@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] KMSAN: uninit-value in hfs_free_fork
Date: Wed, 23 Oct 2024 00:11:55 +0200 [thread overview]
Message-ID: <49b1ba71-1c1e-43e9-a012-42c17f0aad85@gmail.com> (raw)
In-Reply-To: <67182206.050a0220.1e4b4d.007b.GAE@google.com>
[-- Attachment #1: Type: text/plain, Size: 9 bytes --]
#syz test
[-- Attachment #2: 0001-hfs-use-kzalloc-in-hfs_find_init.patch --]
[-- Type: text/x-patch, Size: 770 bytes --]
From 0fb9dbd8a0e88e6e4011c9c97701f40b8d845831 Mon Sep 17 00:00:00 2001
From: Gianfranco Trad <gianf.trad@gmail.com>
Date: Wed, 23 Oct 2024 00:10:04 +0200
Subject: [PATCH] hfs: use kzalloc in hfs_find_init()
Signed-off-by: Gianfranco Trad <gianf.trad@gmail.com>
---
fs/hfs/bfind.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/hfs/bfind.c b/fs/hfs/bfind.c
index ef9498a6e88a..c74d864bc29e 100644
--- a/fs/hfs/bfind.c
+++ b/fs/hfs/bfind.c
@@ -18,7 +18,7 @@ int hfs_find_init(struct hfs_btree *tree, struct hfs_find_data *fd)
fd->tree = tree;
fd->bnode = NULL;
- ptr = kmalloc(tree->max_key_len * 2 + 4, GFP_KERNEL);
+ ptr = kzalloc(tree->max_key_len * 2 + 4, GFP_KERNEL);
if (!ptr)
return -ENOMEM;
fd->search_key = ptr;
--
2.43.0
next prev parent reply other threads:[~2024-10-22 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41a67fa0-52c7-4089-8cb1-3d3d622cbcff@gmail.com>
2024-10-22 22:07 ` [syzbot] [hfs?] KMSAN: uninit-value in hfs_free_fork syzbot
2024-10-22 22:11 ` Gianfranco Trad [this message]
2024-10-22 22:40 ` syzbot
[not found] <6f129270-4c3c-454b-831b-4fe2f5597bc7@gmail.com>
2024-11-11 20:49 ` syzbot
[not found] <429d2bea-ef68-4130-bb8a-0fb5fd38663c@gmail.com>
2024-11-11 20:21 ` syzbot
[not found] <18374947-f71e-4f71-b097-f06eb0699bfa@gmail.com>
2024-11-11 20:21 ` syzbot
2024-05-06 7:01 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=49b1ba71-1c1e-43e9-a012-42c17f0aad85@gmail.com \
--to=gianf.trad@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+2e6fb1f89ce5e13cd02d@syzkaller.appspotmail.com \
--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