From: syzbot <syzbot+9b9124ae9b12d5af5d95@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] KMSAN: kernel-infoleak in vmci_host_unlocked_ioctl (3)
Date: Thu, 19 Jun 2025 21:28:01 -0700 [thread overview]
Message-ID: <6854e351.a00a0220.137b3.002b.GAE@google.com> (raw)
In-Reply-To: <20250620042056.1099990-1-lizhi.xu@windriver.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
drivers/misc/vmw_vmci/vmci_host.c:396:25: error: incompatible integer to pointer conversion passing 'u64' (aka 'unsigned long long') to parameter of type 'const void *' [-Wint-conversion]
Tested on:
commit: 41687a5c Merge tag 'spi-fix-v6.16-rc2' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=61539536677af51c
dashboard link: https://syzkaller.appspot.com/bug?extid=9b9124ae9b12d5af5d95
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
patch: https://syzkaller.appspot.com/x/patch.diff?x=14219d0c580000
next parent reply other threads:[~2025-06-20 4:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250620042056.1099990-1-lizhi.xu@windriver.com>
2025-06-20 4:28 ` syzbot [this message]
[not found] <20250703080919.1229530-1-lizhi.xu@windriver.com>
2025-07-03 10:12 ` [syzbot] [kernel?] KMSAN: kernel-infoleak in vmci_host_unlocked_ioctl (3) syzbot
[not found] <20250627051303.2837086-1-lizhi.xu@windriver.com>
2025-06-27 5:44 ` syzbot
[not found] <20250627032632.2470249-1-lizhi.xu@windriver.com>
2025-06-27 4:54 ` syzbot
[not found] <20250626024902.2942685-1-lizhi.xu@windriver.com>
2025-06-26 4:45 ` syzbot
[not found] <20250626021712.2842722-1-lizhi.xu@windriver.com>
2025-06-26 3:35 ` syzbot
[not found] <20250623094537.3353300-1-lizhi.xu@windriver.com>
2025-06-23 12:11 ` syzbot
[not found] <20250623085022.3182174-1-lizhi.xu@windriver.com>
2025-06-23 9:28 ` syzbot
[not found] <20250623080347.3056823-1-lizhi.xu@windriver.com>
2025-06-23 8:36 ` syzbot
[not found] <20250623030312.2337101-1-lizhi.xu@windriver.com>
2025-06-23 4:28 ` syzbot
[not found] <20250620065432.1558000-1-lizhi.xu@windriver.com>
2025-06-20 10:02 ` syzbot
[not found] <20250620065230.1552640-1-lizhi.xu@windriver.com>
2025-06-20 8:49 ` syzbot
[not found] <20250620052310.1280771-1-lizhi.xu@windriver.com>
2025-06-20 5:58 ` syzbot
[not found] <20250620010300.3380487-1-lizhi.xu@windriver.com>
2025-06-20 2:55 ` syzbot
2025-06-19 23:57 syzbot
2025-06-22 2:37 ` Edward Adam Davis
2025-06-22 3:02 ` syzbot
2025-06-22 4:46 ` Hillf Danton
2025-06-22 5:19 ` syzbot
2025-06-22 6:28 ` Hillf Danton
2025-06-22 7:32 ` syzbot
2025-06-23 12:29 ` Edward Adam Davis
2025-06-23 13:45 ` 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=6854e351.a00a0220.137b3.002b.GAE@google.com \
--to=syzbot+9b9124ae9b12d5af5d95@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.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 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.