[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210701010032.4046a863@gmail.com>
Date: Thu, 1 Jul 2021 01:00:32 +0300
From: Pavel Skripkin <paskripkin@...il.com>
To: syzbot <syzbot+44e40ac2cfe68e8ce207@...kaller.appspotmail.com>
Cc: alex.dewar90@...il.com, arnd@...db.de, gregkh@...uxfoundation.org,
hdanton@...a.com, jhansen@...are.com, linux-kernel@...r.kernel.org,
snovitoll@...il.com, syzkaller-bugs@...glegroups.com,
vdasa@...are.com
Subject: Re: [syzbot] possible deadlock in vmci_qp_broker_detach
On Wed, 30 Jun 2021 14:56:06 -0700
syzbot <syzbot+44e40ac2cfe68e8ce207@...kaller.appspotmail.com> wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer is still
> triggering an issue: INFO: task hung in vmci_ctx_destroy
>
> INFO: task syz-executor.4:4967 blocked for more than 143 seconds.
> Tainted: G W 5.13.0-syzkaller #0
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
> message. task:syz-executor.4 state:D stack:29136 pid: 4967 ppid:
> 8823 flags:0x00004004 Call Trace:
Hmm, I forgot to change old vmci_ctx_put() in
vmci_ctx_enqueue_datagram()...
#syz test
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
With regards,
Pavel Skripkin
View attachment "0001-misc-vmv_vmci-fix-deadlock.patch" of type "text/x-patch" (5067 bytes)
Powered by blists - more mailing lists