From: Jeongjun Park <aha310510@gmail.com>
To: syzbot+6c21aeb59d0e82eb2782@syzkaller.appspotmail.com
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [virt?] [net?] KMSAN: uninit-value in vsock_assign_transport (2)
Date: Fri, 19 Apr 2024 21:39:59 +0900 [thread overview]
Message-ID: <20240419123959.8572-1-aha310510@gmail.com> (raw)
In-Reply-To: <000000000000be4e1c06166fdc85@google.com>
please test uninit-value in vsock_assign_transport
#syz test git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
---
drivers/vhost/vsock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/vhost/vsock.c b/drivers/vhost/vsock.c
index ec20ecff85c7..652ef97a444b 100644
--- a/drivers/vhost/vsock.c
+++ b/drivers/vhost/vsock.c
@@ -656,7 +656,7 @@ static int vhost_vsock_dev_open(struct inode *inode, struct file *file)
/* This struct is large and allocation could fail, fall back to vmalloc
* if there is no other way.
*/
- vsock = kvmalloc(sizeof(*vsock), GFP_KERNEL | __GFP_RETRY_MAYFAIL);
+ vsock = kvzmalloc(sizeof(*vsock), GFP_KERNEL | __GFP_RETRY_MAYFAIL);
if (!vsock)
return -ENOMEM;
--
2.34.1
next prev parent reply other threads:[~2024-04-19 12:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 9:39 syzbot
2024-04-19 12:39 ` Jeongjun Park [this message]
2024-04-19 14:44 ` syzbot
2024-04-19 14:56 ` Jeongjun Park
2024-04-19 15:39 ` syzbot
2024-04-20 8:57 ` [PATCH virt] virt: fix uninit-value in vhost_vsock_dev_open Jeongjun Park
2024-04-20 10:05 ` Michael S. Tsirkin
2024-04-21 3:06 ` Jeongjun Park
2024-04-22 13:00 ` Stefan Hajnoczi
2024-04-22 14:20 ` Michael S. Tsirkin
2024-05-05 19:53 ` Arseniy Krasnov
2024-04-22 14:18 ` [syzbot] [virt?] [net?] KMSAN: uninit-value in vsock_assign_transport (2) Michael S. Tsirkin
2024-04-23 1:31 ` 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=20240419123959.8572-1-aha310510@gmail.com \
--to=aha310510@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+6c21aeb59d0e82eb2782@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
all inboxes | Powered by JetHome®