similar to: Reminder: 2 open syzbot bugs in vhost subsystem

Displaying 20 results from an estimated 4000 matches similar to: "Reminder: 2 open syzbot bugs in vhost subsystem"

2019 Jul 02
0
Reminder: 2 open syzbot bugs in vhost subsystem
On 2019/7/2 ??1:17, Eric Biggers wrote: > [This email was generated by a script. Let me know if you have any suggestions > to make it better, or if you want it re-generated with the latest status.] > > Of the currently open syzbot reports against the upstream kernel, I've manually > marked 2 of them as possibly being bugs in the vhost subsystem. I've listed > these
2019 Jul 24
1
Reminder: 3 open syzbot bugs in vhost subsystem
On 2019/7/24 ??10:38, Eric Biggers wrote: > [This email was generated by a script. Let me know if you have any suggestions > to make it better, or if you want it re-generated with the latest status.] > > Of the currently open syzbot reports against the upstream kernel, I've manually > marked 3 of them as possibly being bugs in the vhost subsystem. I've listed > these
2019 Jul 02
0
Reminder: 2 open syzbot bugs in vhost subsystem
On Tue, 2 Jul 2019 13:30:07 +0800 Jason Wang wrote: > On 2019/7/2 Eric Biggers wrote: > > [This email was generated by a script. Let me know if you have any suggestions > > to make it better, or if you want it re-generated with the latest status.] > > > > Of the currently open syzbot reports against the upstream kernel, I've manually > > marked 2 of them as
2023 Jun 10
2
[Bridge] [syzbot] [net?] unregister_netdevice: waiting for DEV to become free (8)
Hello, syzbot found the following issue on: HEAD commit: 67faabbde36b selftests/bpf: Add missing prototypes for sev.. git tree: bpf-next console+strace: https://syzkaller.appspot.com/x/log.txt?x=1381363b280000 kernel config: https://syzkaller.appspot.com/x/.config?x=5335204dcdecfda dashboard link: https://syzkaller.appspot.com/bug?extid=881d65229ca4f9ae8c84 compiler: gcc (Debian
2018 Aug 08
0
KASAN: use-after-free Read in iotlb_access_ok
On 2018?08?07? 19:16, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:??? e30cb13c5a09 Merge > git://git.kernel.org/pub/scm/linux/kern.. > git tree:?????? upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=10a153e0400000 > kernel config: https://syzkaller.appspot.com/x/.config?x=2dc0cd7c2eefb46f > dashboard link:
2023 May 30
1
[syzbot] [kvm?] [net?] [virt?] general protection fault in vhost_work_queue
On Tue, May 30, 2023 at 12:30:06AM -0700, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: 933174ae28ba Merge tag 'spi-fix-v6.4-rc3' of git://git.ker.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=138d4ae5280000 > kernel config: https://syzkaller.appspot.com/x/.config?x=f389ffdf4e9ba3f0
2022 Oct 16
0
[syzbot] net boot error: WARNING in cpumask_next_wrap
On Sat, Oct 15, 2022 at 12:21:41PM -0700, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: a1b6b102df03 Merge branch 'phylink_set_mac_pm' > git tree: net > console output: https://syzkaller.appspot.com/x/log.txt?x=179af0c2880000 > kernel config: https://syzkaller.appspot.com/x/.config?x=85495c44a2c25446 > dashboard
2018 Apr 09
2
kernel BUG at drivers/vhost/vhost.c:LINE! (2)
On Sat, Apr 7, 2018 at 3:02 AM, syzbot <syzbot+65a84dde0214b0387ccd at syzkaller.appspotmail.com> wrote: > syzbot hit the following crash on upstream commit > 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +0000) > Merge tag 'armsoc-drivers' of > git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc > syzbot dashboard link: >
2018 Apr 09
2
kernel BUG at drivers/vhost/vhost.c:LINE! (2)
On Sat, Apr 7, 2018 at 3:02 AM, syzbot <syzbot+65a84dde0214b0387ccd at syzkaller.appspotmail.com> wrote: > syzbot hit the following crash on upstream commit > 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +0000) > Merge tag 'armsoc-drivers' of > git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc > syzbot dashboard link: >
2019 Oct 04
0
general protection fault in veth_get_stats64
On Wed, Oct 2, 2019 at 5:45 PM syzbot <syzbot+3f3e5e77d793c7a6fe6c at syzkaller.appspotmail.com> wrote: > > Hello, > > syzbot found the following crash on: > > HEAD commit: a32db7e1 Add linux-next specific files for 20191002 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=175ab7cd600000 > kernel config:
2018 Jul 05
0
KASAN: stack-out-of-bounds Read in __netif_receive_skb_core
On Thu, Jul 5, 2018 at 6:59 AM, syzbot <syzbot+4e955f82549d361ed655 at syzkaller.appspotmail.com> wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit: 2bdea157b999 Merge branch 'sctp-fully-support-for-dscp-and.. > git tree: bpf-next > console output: https://syzkaller.appspot.com/x/log.txt?x=178c5e68400000 > kernel config:
2023 Mar 27
0
[syzbot] [net?] [virt?] [io-uring?] [kvm?] BUG: soft lockup in vsock_connect
On Sat, Mar 25, 2023 at 1:44?AM Bobby Eshleman <bobbyeshleman at gmail.com> wrote: > > On Fri, Mar 24, 2023 at 09:38:38AM +0100, Stefano Garzarella wrote: > > Hi Bobby, > > FYI we have also this one, but it seems related to > > syzbot+befff0a9536049e7902e at syzkaller.appspotmail.com > > > > Thanks, > > Stefano > > > > Got it, I'll
2019 Jul 02
0
INFO: task hung in vhost_init_device_iotlb
On 2019/1/30 ??4:12, Dmitry Vyukov wrote: > On Tue, Jan 29, 2019 at 5:06 PM Michael S. Tsirkin<mst at redhat.com> wrote: >> On Tue, Jan 29, 2019 at 01:22:02AM -0800, syzbot wrote: >>> Hello, >>> >>> syzbot found the following crash on: >>> >>> HEAD commit: 983542434e6b Merge tag 'edac_fix_for_5.0' of git://git.ker..
2020 Apr 06
0
upstream boot error: KASAN: slab-out-of-bounds Write in virtio_gpu_object_create
On Mon, Apr 06, 2020 at 09:07:44AM +0200, Dmitry Vyukov wrote: > On Mon, Apr 6, 2020 at 8:46 AM syzbot > <syzbot+d3a7951ed361037407db at syzkaller.appspotmail.com> wrote: > > > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit: ffc1c20c Merge tag 'for-5.7/dm-changes' of git://git.kerne.. > > git tree:
2019 Mar 25
2
INFO: task hung in vhost_net_stop_vq
Looks like more iotlb locking mess? On Tue, Mar 19, 2019 at 10:21:00PM -0700, syzbot wrote: > syzbot has bisected this bug to: > > commit 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c > Author: Jason Wang <jasowang at redhat.com> > Date: Thu Jun 23 06:04:32 2016 +0000 > > vhost: new device IOTLB API > > bisection log:
2019 Mar 25
2
INFO: task hung in vhost_net_stop_vq
Looks like more iotlb locking mess? On Tue, Mar 19, 2019 at 10:21:00PM -0700, syzbot wrote: > syzbot has bisected this bug to: > > commit 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c > Author: Jason Wang <jasowang at redhat.com> > Date: Thu Jun 23 06:04:32 2016 +0000 > > vhost: new device IOTLB API > > bisection log:
2019 Jul 27
2
INFO: rcu detected stall in vhost_worker
Fri, 26 Jul 2019 08:26:01 -0700 (PDT) > syzbot has bisected this bug to: > > commit 0ecfebd2b52404ae0c54a878c872bb93363ada36 > Author: Linus Torvalds <torvalds at linux-foundation.org> > Date: Sun Jul 7 22:41:56 2019 +0000 > > Linux 5.2 > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=118810bfa00000 > start commit: 13bf6d6a Add
2019 Oct 02
0
general protection fault in veth_get_stats64
On Wed, Oct 2, 2019 at 3:56 PM syzbot <syzbot+3f3e5e77d793c7a6fe6c at syzkaller.appspotmail.com> wrote: > > Hello, > > syzbot found the following crash on: > > HEAD commit: a32db7e1 Add linux-next specific files for 20191002 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=175ab7cd600000 > kernel config:
2019 Sep 06
0
possible deadlock in __mmu_notifier_invalidate_range_end
Hello, syzbot found the following crash on: HEAD commit: 6d028043 Add linux-next specific files for 20190830 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=16cbf22a600000 kernel config: https://syzkaller.appspot.com/x/.config?x=82a6bec43ab0cb69 dashboard link: https://syzkaller.appspot.com/bug?extid=aaedc50d99a03250fe1f compiler: gcc (GCC) 9.0.0
2019 Mar 26
1
INFO: task hung in vhost_net_stop_vq
On Tue, Mar 26, 2019 at 11:17 AM Jason Wang <jasowang at redhat.com> wrote: > > > On 2019/3/25 ??10:02, Michael S. Tsirkin wrote: > > Looks like more iotlb locking mess? > > > Looking at the calltrace: > > [ 221.743675] ============================================= > [ 221.744297] [ INFO: possible recursive locking detected ] > [ 221.744944] 4.7.0+ #1