[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <xx2igtwgro5ffbmdaahbwz6irolnfh4ktmdfatfrl72kppne7m@rp2ajscxfpp2>
Date: Tue, 11 Feb 2025 09:13:36 +0100
From: Stefano Garzarella <sgarzare@...hat.com>
To: syzbot <syzbot+71613b464c8ef17ab718@...kaller.appspotmail.com>
Cc: bobby.eshleman@...edance.com, davem@...emloft.net, edumazet@...gle.com,
horms@...nel.org, kuba@...nel.org, leonardi@...hat.com,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org, pabeni@...hat.com,
syzkaller-bugs@...glegroups.com, v4bel@...ori.io, virtualization@...ts.linux-foundation.org,
virtualization@...ts.linux.dev
Subject: Re: [syzbot] [net?] [virt?] general protection fault in
vsock_stream_has_data
#syz fix: vsock/virtio: cancel close work in the destructor
On Mon, Feb 10, 2025 at 05:30:04PM -0800, syzbot wrote:
>syzbot suspects this issue was fixed by commit:
>
>commit df137da9d6d166e87e40980e36eb8e0bc90483ef
>Author: Stefano Garzarella <sgarzare@...hat.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
>
Powered by blists - more mailing lists