Re: possible deadlock in io_poll_double_wake (2)

2021-03-03 Thread Jens Axboe
On 3/2/21 11:52 PM, Hillf Danton wrote: > Tue, 02 Mar 2021 10:59:05 -0800 >> Hello, >> >> syzbot has tested the proposed patch but the reproducer is still triggering >> an issue: >> possible deadlock in io_poll_double_wake >> >> >> WARNING: possible rec

Re: possible deadlock in io_poll_double_wake (2)

2021-03-03 Thread syzbot
Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: possible deadlock in io_poll_double_wake poll and dpoll head different WARNING: possible recursive locking detected 5.12.0-rc1-syzkaller #0 Not tainted --

Re: possible deadlock in io_poll_double_wake (2)

2021-03-03 Thread Jens Axboe
On 3/2/21 11:59 AM, syzbot wrote: > Hello, > > syzbot has tested the proposed patch but the reproducer is still triggering > an issue: > possible deadlock in io_poll_double_wake > > > WARNING: possible recursive locking detected > 5.12.0-rc1-syzkaller

Re: possible deadlock in io_poll_double_wake (2)

2021-03-02 Thread syzbot
Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: possible deadlock in io_poll_double_wake WARNING: possible recursive locking detected 5.12.0-rc1-syzkaller #0 Not tainted

Re: possible deadlock in io_poll_double_wake (2)

2021-03-02 Thread Jens Axboe
On 2/28/21 9:18 PM, syzbot wrote: > Hello, > > syzbot has tested the proposed patch but the reproducer is still triggering > an issue: > possible deadlock in io_poll_double_wake > > > WARNING: possible recursive locking detected > 5.11.0-syzkaller #0

Re: possible deadlock in io_poll_double_wake (2)

2021-03-01 Thread syzbot
Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: possible deadlock in io_poll_double_wake WARNING: possible recursive locking detected 5.11.0-syzkaller #0 Not tainted

Re: possible deadlock in io_poll_double_wake (2)

2021-03-01 Thread Jens Axboe
#syz test: git://git.kernel.dk/linux-block syzbot-test -- Jens Axboe

Re: possible deadlock in io_poll_double_wake (2)

2021-02-28 Thread syzbot
Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: possible deadlock in io_poll_double_wake WARNING: possible recursive locking detected 5.11.0-syzkaller #0 Not tainted

Re: possible deadlock in io_poll_double_wake (2)

2021-02-28 Thread Jens Axboe
On 2/27/21 5:42 PM, syzbot wrote: > syzbot has found a reproducer for the following issue on: > > HEAD commit:5695e516 Merge tag 'io_uring-worker.v3-2021-02-25' of git:.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=114e3866d0 > kernel config: htt

Re: possible deadlock in io_poll_double_wake (2)

2021-02-27 Thread syzbot
syzbot has found a reproducer for the following issue on: HEAD commit:5695e516 Merge tag 'io_uring-worker.v3-2021-02-25' of git:.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=114e3866d0 kernel config: https://syzkaller.appspot.com/x/.config?x=8c76dad

Re: possible deadlock in io_poll_double_wake

2020-08-15 Thread Jens Axboe
#syz dup general protection fault in io_poll_double_wake -- Jens Axboe

Re: possible deadlock in io_poll_double_wake

2020-08-15 Thread Jens Axboe
#syz dupe general protection fault in io_poll_double_wake -- Jens Axboe

Re: possible deadlock in io_poll_double_wake

2020-08-15 Thread syzbot
syzbot has found a reproducer for the following issue on: HEAD commit:c9c9735c Merge tag 'scsi-misc' of git://git.kernel.org/pub.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=165d3b6a90 kernel config: https://syzkaller.appspot.com/x/.config?x=adea84f

Re: Re: possible deadlock in io_poll_double_wake

2020-08-15 Thread syzbot
> #syz dupe general protection fault in io_poll_double_wake unknown command "dupe" > > -- > Jens Axboe >

Re: Re: possible deadlock in io_poll_double_wake

2020-08-15 Thread syzbot
> #syz dupe general protection fault in io_poll_double_wake unknown command "dupe" > > -- > Jens Axboe > > -- > You received this message because you are subscribed to the Google Groups > "syzkaller-bugs" group. > To unsubscribe from this group and stop receiving emails from it, send an > ema