mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Juan Perdomo <jcperdomo100@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzbot+0cece8fa7d83523f47a3@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup
Date: Mon, 14 Sep 2026 14:30:10 +0000	[thread overview]
Message-ID: <178939621037.604238.10748160763592538123.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260913030945.4011-1-jcperdomo100@gmail.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Sat, 12 Sep 2026 23:09:45 -0400 you wrote:
> rfcomm_sock_cleanup_listen() closes unaccepted child sockets through
> rfcomm_sock_close(), which takes the child socket lock before
> rfcomm_dlc_close() acquires rfcomm_mutex. The RFCOMM worker takes these
> locks in reverse order while handling connections and DLC state changes,
> so lockdep reports a possible deadlock.
> 
> Close dequeued children without taking their socket lock. The accept queue
> owns a reference to each child, and bt_accept_dequeue() locks the child
> while unlinking it and clearing its parent pointer.
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup
    https://git.kernel.org/bluetooth/bluetooth-next/c/0186e4e1e5c2

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-09-14 14:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 16:09 [syzbot] [bluetooth?] possible deadlock in rfcomm_dlc_close syzbot
2026-09-12 20:49 ` Forwarded: [PATCH] Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup syzbot
2026-09-13  1:51 ` Forwarded: [PATCH v2] " syzbot
2026-09-13  3:09 ` Juan Perdomo
2026-09-14 14:30   ` patchwork-bot+bluetooth [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=178939621037.604238.10748160763592538123.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=jcperdomo100@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=syzbot+0cece8fa7d83523f47a3@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®