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, kees@kernel.org,
	kuba@kernel.org, pengpeng@iscas.ac.cn, yaojiale02@163.com,
	suunj1331@gmail.com, ali@iusegentoo.com, tim.bird@sony.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	pav@iki.fi
Subject: Re: [PATCH v2] Bluetooth: RFCOMM: serialize session teardown
Date: Mon, 24 Aug 2026 16:50:07 +0000	[thread overview]
Message-ID: <178759020713.3014491.3447283705707254634.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260822150619.3684599-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 Sat, 22 Aug 2026 23:06:19 +0800 you wrote:
> rfcomm_kill_listener() walks session_list and deletes every session
> without holding rfcomm_mutex, unlike the normal session processing and
> connect error paths.
> 
> Under normal operation, an open RFCOMM socket pins rfcomm.ko, so
> rfcomm_kill_listener() does not run concurrently with rfcomm_dlc_open().
> However, forced module unload via delete_module(O_TRUNC) can stop
> krfcommd while a failed connect is still unwinding.
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: RFCOMM: serialize session teardown
    https://git.kernel.org/bluetooth/bluetooth-next/c/fe3897b4ab57

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-08-24 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 15:06 [PATCH v2] Bluetooth: RFCOMM: serialize session teardown Chengfeng Ye
2026-08-22 15:44 ` [v2] " bluez.test.bot
2026-08-24 16:50 ` 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=178759020713.3014491.3447283705707254634.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=ali@iusegentoo.com \
    --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=pav@iki.fi \
    --cc=pengpeng@iscas.ac.cn \
    --cc=suunj1331@gmail.com \
    --cc=tim.bird@sony.com \
    --cc=yaojiale02@163.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.