From: syzbot <syzbot+befff0a9536049e7902e@syzkaller•appspotmail.com>
To: avkrasnov@sberdevices•ru, bobby.eshleman@bytedance•com,
bobby.eshleman@gmail•com, davem@davemloft•net,
edumazet@google•com, kuba@kernel•org, kvm@vger•kernel.org,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
oxffffaa@gmail•com, pabeni@redhat•com, sgarzare@redhat•com,
stefanha@redhat•com, syzkaller-bugs@googlegroups•com,
virtualization@lists•linux-foundation.org
Subject: Re: [syzbot] [kvm?] [net?] [virt?] general protection fault in virtio_transport_purge_skbs
Date: Fri, 24 Mar 2023 02:12:19 -0700 [thread overview]
Message-ID: <000000000000480a6c05f7a1ca68@google.com> (raw)
In-Reply-To: <CAGxU2F6m4KWXwOF8StjWbb=S6HRx=GhV_ONDcZxCZsDkvuaeUg@mail.gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
net/vmw_vsock/vsock_loopback.c:155:21: error: 'struct vsock_loopback' has no member named 'pkt_list_lock'
net/vmw_vsock/vsock_loopback.c:157:23: error: 'struct vsock_loopback' has no member named 'pkt_list_lock'
Tested on:
commit: fff5a5e7 Merge tag 'for-linus' of git://git.armlinux.o..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
dashboard link: https://syzkaller.appspot.com/bug?extid=befff0a9536049e7902e
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=15ed6191c80000
next prev parent reply other threads:[~2023-03-24 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 0:52 [syzbot] [kvm?] [net?] [virt?] general protection fault in virtio_transport_purge_skbs syzbot
2023-03-24 8:31 ` Stefano Garzarella
2023-03-24 8:55 ` Stefano Garzarella
2023-03-24 9:06 ` Stefano Garzarella
2023-03-24 9:06 ` Arseniy Krasnov
2023-03-24 9:30 ` Stefano Garzarella
2023-03-24 9:13 ` syzbot
2023-03-24 11:58 ` Stefano Garzarella
2023-03-24 9:12 ` syzbot [this message]
2023-03-26 22:45 ` syzbot
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=000000000000480a6c05f7a1ca68@google.com \
--to=syzbot+befff0a9536049e7902e@syzkaller$(echo .)appspotmail.com \
--cc=avkrasnov@sberdevices$(echo .)ru \
--cc=bobby.eshleman@bytedance$(echo .)com \
--cc=bobby.eshleman@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=oxffffaa@gmail$(echo .)com \
--cc=pabeni@redhat$(echo .)com \
--cc=sgarzare@redhat$(echo .)com \
--cc=stefanha@redhat$(echo .)com \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=virtualization@lists$(echo .)linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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