From: syzbot <syzbot+3affdbfc986ecd9200fd@syzkaller.appspotmail.com>
To: cong.wang@bytedance.com, davem@davemloft.net,
edumazet@google.com, horms@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, mst@redhat.com,
netdev@vger.kernel.org, pabeni@redhat.com, sgarzare@redhat.com,
syzkaller-bugs@googlegroups.com, virtualization@lists.linux.dev
Subject: Re: [syzbot] [virt?] [net?] general protection fault in vsock_connectible_has_data
Date: Thu, 09 Jan 2025 02:15:03 -0800 [thread overview]
Message-ID: <677fa1a7.050a0220.25a300.01b5.GAE@google.com> (raw)
In-Reply-To: <a4n77w3u22efhdnyz5xn5gjvsfq7xncy3lyn32xqobnuw6gb27@kxubdyn4hr2q>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+3affdbfc986ecd9200fd@syzkaller.appspotmail.com
Tested-by: syzbot+3affdbfc986ecd9200fd@syzkaller.appspotmail.com
Tested on:
commit: 767faff2 vsock/bpf: return early if transport is not a..
git tree: https://github.com/stefano-garzarella/linux.git fix-vsock-null-transport
console output: https://syzkaller.appspot.com/x/log.txt?x=17c9d4b0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4ef22c4fce5135b4
dashboard link: https://syzkaller.appspot.com/bug?extid=3affdbfc986ecd9200fd
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2025-01-09 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 8:11 [syzbot] [virt?] [net?] general protection fault in vsock_connectible_has_data syzbot
2025-01-09 8:33 ` Stefano Garzarella
2025-01-09 10:15 ` syzbot [this message]
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=677fa1a7.050a0220.25a300.01b5.GAE@google.com \
--to=syzbot+3affdbfc986ecd9200fd@syzkaller.appspotmail.com \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=virtualization@lists.linux.dev \
/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