From: patchwork-bot+bluetooth@kernel.org
To: Bui Viet Dung <dungvn2345@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: selftest: Pin module for selftest debugfs file operations
Date: Fri, 09 Oct 2026 14:20:15 +0000 [thread overview]
Message-ID: <179155561501.812174.1610963869730671308.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261008051803.526248-1-dungvn2345@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 8 Oct 2026 12:18:03 +0700 you wrote:
> An open debugfs file retains its file_operations pointer in the
> debugfs proxy state. However, test_smp_fops in net/bluetooth/smp.c and
> test_ecdh_fops in net/bluetooth/selftest.c have no .owner set to
> THIS_MODULE.
>
> As a result, full_proxy_open_regular() calls fops_get() which succeeds
> without taking a reference to the bluetooth module. When CONFIG_BT=m
> and selftests are enabled, a userspace process can open either
> /sys/kernel/debug/bluetooth/selftest_smp or
> /sys/kernel/debug/bluetooth/selftest_ecdh and keep the file descriptor
> open while the module is unloaded (rmmod bluetooth).
>
> [...]
Here is the summary with links:
- Bluetooth: selftest: Pin module for selftest debugfs file operations
https://git.kernel.org/bluetooth/bluetooth-next/c/839c7cdc250c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-09 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 5:18 [PATCH] Bluetooth: selftest: Pin module for selftest debugfs file operations Bui Viet Dung
2026-10-08 7:57 ` bluez.test.bot
2026-10-09 14:20 ` 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=179155561501.812174.1610963869730671308.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=dungvn2345@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=stable@vger.kernel.org \
/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