[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <691707ba.a70a0220.3124cb.004c.GAE@google.com>
Date: Fri, 14 Nov 2025 02:43:06 -0800
From: syzbot <syzbot+7902f127c28c701e913f@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Forwarded: Re: [syzbot] [mptcp?] possible deadlock in
mptcp_subflow_shutdown (2)
For archival purposes, forwarding an incoming command email to
linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com.
***
Subject: Re: [syzbot] [mptcp?] possible deadlock in mptcp_subflow_shutdown (2)
Author: matttbe@...nel.org
On 14/11/2025 11:27, syzbot wrote:
>> On 10/11/2025 09:41, Paolo Abeni wrote:
(...)
>> As noted by Paolo offline, it looks like this issue is due to nbd
>> introducing a lockdep dependency between reclaim and af_socket, and this
>> is similar to a previous report:
>>
>> #syz dup: [syzbot] [mptcp?] possible deadlock in
>
> can't find the dup bug
Line wrapping... What about this?
#syz dup: [syzbot] [mptcp?] possible deadlock in mptcp_subflow_create_socket (2)
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
Powered by blists - more mailing lists