From: syzbot <syzbot+71613b464c8ef17ab718@syzkaller.appspotmail.com>
To: bobby.eshleman@bytedance.com, davem@davemloft.net,
edumazet@google.com, horms@kernel.org, kuba@kernel.org,
leonardi@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, sgarzare@redhat.com,
syzkaller-bugs@googlegroups.com, v4bel@theori.io,
virtualization@lists.linux-foundation.org,
virtualization@lists.linux.dev
Subject: Re: [syzbot] [net?] [virt?] general protection fault in vsock_stream_has_data
Date: Mon, 10 Feb 2025 17:30:04 -0800 [thread overview]
Message-ID: <67aaa81c.050a0220.3d72c.0059.GAE@google.com> (raw)
In-Reply-To: <67867937.050a0220.216c54.007c.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit df137da9d6d166e87e40980e36eb8e0bc90483ef
Author: Stefano Garzarella <sgarzare@redhat.com>
Date: Fri Jan 10 08:35:09 2025 +0000
vsock/virtio: cancel close work in the destructor
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12bb31b0580000
start commit: 25cc469d6d34 net: phy: micrel: use helper phy_disable_eee
git tree: net-next
kernel config: https://syzkaller.appspot.com/x/.config?x=d50f1d63eac02308
dashboard link: https://syzkaller.appspot.com/bug?extid=71613b464c8ef17ab718
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=125a3218580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=147f11df980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: vsock/virtio: cancel close work in the destructor
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-02-11 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 14:48 [syzbot] [net?] [virt?] general protection fault in vsock_stream_has_data syzbot
2025-01-14 14:56 ` Stefano Garzarella
2025-01-14 15:40 ` syzbot
2025-02-11 1:30 ` syzbot [this message]
2025-02-11 8:13 ` Stefano Garzarella
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=67aaa81c.050a0220.3d72c.0059.GAE@google.com \
--to=syzbot+71613b464c8ef17ab718@syzkaller.appspotmail.com \
--cc=bobby.eshleman@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leonardi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v4bel@theori.io \
--cc=virtualization@lists.linux-foundation.org \
--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