From: syzbot <syzbot+2479e53d0db9b32ae2aa@syzkaller.appspotmail.com>
To: hdanton@sina.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, seanjc@google.com,
syzkaller-bugs@googlegroups.com, tabba@google.com,
xiaoyao.li@intel.com
Subject: Re: [syzbot] [kvm?] KASAN: slab-use-after-free Write in kvm_gmem_release
Date: Fri, 24 Oct 2025 20:42:04 -0700 [thread overview]
Message-ID: <68fc470c.a00a0220.9662e.0012.GAE@google.com> (raw)
In-Reply-To: <20251025015852.8771-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+2479e53d0db9b32ae2aa@syzkaller.appspotmail.com
Tested-by: syzbot+2479e53d0db9b32ae2aa@syzkaller.appspotmail.com
Tested on:
commit: 72fb0170 Add linux-next specific files for 20251024
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15da53e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bcaf4aad77308158
dashboard link: https://syzkaller.appspot.com/bug?extid=2479e53d0db9b32ae2aa
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=161c4258580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-10-25 3:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 18:55 [syzbot] [kvm?] KASAN: slab-use-after-free Write in kvm_gmem_release syzbot
2025-10-24 6:15 ` syzbot
2025-10-24 19:14 ` Sean Christopherson
2025-10-24 20:10 ` syzbot
2025-10-24 23:24 ` Hillf Danton
2025-10-24 23:27 ` syzbot
2025-10-24 23:43 ` Hillf Danton
2025-10-25 0:12 ` syzbot
2025-10-25 1:58 ` Hillf Danton
2025-10-25 3:42 ` syzbot [this message]
2025-10-27 14:41 ` Sean Christopherson
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=68fc470c.a00a0220.9662e.0012.GAE@google.com \
--to=syzbot+2479e53d0db9b32ae2aa@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tabba@google.com \
--cc=xiaoyao.li@intel.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.