All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Chengfeng Ye <nicoyip.dev@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, kuba@kernel.org,
	broonie@kernel.org, johan@kernel.org, tim.bird@sony.com,
	kees@kernel.org, peter@hurleysoftware.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: RFCOMM: Fix initial port reference race
Date: Mon, 28 Sep 2026 15:40:28 +0000	[thread overview]
Message-ID: <179061002863.4169639.16838238725128380155.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260926172723.2405885-1-nicoyip.dev@gmail.com>

Hello:

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

On Sun, 27 Sep 2026 01:27:23 +0800 you wrote:
> For RFCOMM_RELEASE_ONHUP devices, rfcomm_tty_install() and
> __rfcomm_release_dev() both use RFCOMM_TTY_OWNED to decide who drops the
> initial tty_port reference. The release path tests the bit separately
> from the install path setting it, so both can drop that reference.
> 
> The synchronous hangup does not prevent this race: port->tty is not
> assigned until tty_port_open(), after installation. The following
> interleaving is possible:
> 
> [...]

Here is the summary with links:
  - Bluetooth: RFCOMM: Fix initial port reference race
    https://git.kernel.org/bluetooth/bluetooth-next/c/2d696c1ed346

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



      parent reply	other threads:[~2026-09-28 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-26 17:27 [PATCH] Bluetooth: RFCOMM: Fix initial port reference race Chengfeng Ye
2026-09-27 23:23 ` bluez.test.bot
2026-09-28 15:40 ` 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=179061002863.4169639.16838238725128380155.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=broonie@kernel.org \
    --cc=johan@kernel.org \
    --cc=kees@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=nicoyip.dev@gmail.com \
    --cc=peter@hurleysoftware.com \
    --cc=stable@vger.kernel.org \
    --cc=tim.bird@sony.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.