public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7902f127c28c701e913f@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] [mptcp?] possible deadlock in mptcp_subflow_shutdown (2)
Date: Fri, 14 Nov 2025 02:43:06 -0800	[thread overview]
Message-ID: <691707ba.a70a0220.3124cb.004c.GAE@google.com> (raw)
In-Reply-To: <69113ffc.a70a0220.22f260.00cd.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: Re: [syzbot] [mptcp?] possible deadlock in mptcp_subflow_shutdown (2)
Author: matttbe@kernel.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.


      parent reply	other threads:[~2025-11-14 10:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10  1:29 [syzbot] [mptcp?] possible deadlock in mptcp_subflow_shutdown (2) syzbot
2025-11-10  8:41 ` Paolo Abeni
2025-11-14 10:27   ` Matthieu Baerts
2025-11-14 10:27     ` syzbot
2025-11-14 10:43 ` syzbot [this message]

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=691707ba.a70a0220.3124cb.004c.GAE@google.com \
    --to=syzbot+7902f127c28c701e913f@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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