mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: 6lowpan: Pin module for 6lowpan_control debugfs file
Date: Fri, 09 Oct 2026 14:20:06 +0000	[thread overview]
Message-ID: <179155560628.812174.5344547417953773024.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261008051129.508322-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:11:29 +0700 you wrote:
> An open debugfs file retains lowpan_control_fops in the debugfs proxy
> state. However, lowpan_control_fops has 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_6lowpan module.
> 
> With CONFIG_BT_6LOWPAN=m, a userspace process can keep the debugfs file
> descriptor for 6lowpan_control open across module unload
> (delete_module / rmmod bluetooth_6lowpan). When the process subsequently
> closes the file descriptor, full_proxy_release() accesses the already
> freed and unmapped lowpan_control_fops table, causing a kernel page fault
> or oops.
> 
> [...]

Here is the summary with links:
  - Bluetooth: 6lowpan: Pin module for 6lowpan_control debugfs file
    https://git.kernel.org/bluetooth/bluetooth-next/c/b019e48cee2d

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



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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08  5:11 Bui Viet Dung
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=179155560628.812174.5344547417953773024.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
all inboxes | Powered by JetHome®