From: syzbot <syzbot+ac856b8b866cca41352c@syzkaller.appspotmail.com>
To: eperezma@redhat.com, jasowang@redhat.com,
linux-kernel@vger.kernel.org, mst@redhat.com,
syzkaller-bugs@googlegroups.com, virtualization@lists.linux.dev,
xuanzhuo@linux.alibaba.com
Subject: Re: [syzbot] [virt?] upstream test error: KMSAN: use-after-free in vring_map_one_sg
Date: Sat, 11 Oct 2025 02:20:02 -0700 [thread overview]
Message-ID: <68ea2142.050a0220.91a22.01cb.GAE@google.com> (raw)
In-Reply-To: <CACGkMEtnrayDWKFdJ1P22QyCrZuDK0C2LihhOtvhUyTOKSp_HQ@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+ac856b8b866cca41352c@syzkaller.appspotmail.com
Tested-by: syzbot+ac856b8b866cca41352c@syzkaller.appspotmail.com
Tested on:
commit: 07394736 Merge tag 'for-6.18/hpfs-changes' of git://gi..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=60ff1a9f60b0f77d
dashboard link: https://syzkaller.appspot.com/bug?extid=ac856b8b866cca41352c
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=17a7a9e2580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-10-11 9:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 20:38 [syzbot] [virt?] upstream test error: KMSAN: use-after-free in vring_map_one_sg syzbot
2025-10-11 7:40 ` Jason Wang
2025-10-11 9:20 ` syzbot [this message]
2025-10-13 5:29 ` Jason Wang
2025-10-13 7:20 ` Jason Wang
2025-10-13 7:37 ` Paolo Abeni
2025-10-13 8:08 ` Michael S. Tsirkin
2025-10-13 8:17 ` Paolo Abeni
2025-10-14 2:41 ` Jason Wang
2025-10-14 6:47 ` Paolo Abeni
2025-10-14 2:38 ` Jason Wang
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=68ea2142.050a0220.91a22.01cb.GAE@google.com \
--to=syzbot+ac856b8b866cca41352c@syzkaller.appspotmail.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).