All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Cen Zhang <zzzccc427@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, baijiaju1990@gmail.com
Subject: Re: [PATCH] Bluetooth: 6lowpan: avoid untracked enable work
Date: Fri, 26 Jun 2026 11:16:44 +0000	[thread overview]
Message-ID: <178247260405.3816447.9539369733535711581.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260623161229.2174546-1-zzzccc427@gmail.com>

Hello:

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

On Wed, 24 Jun 2026 00:12:29 +0800 you wrote:
> lowpan_enable_set() allocates a temporary work item and schedules
> do_enable_set() on system_wq, then returns to debugfs. The debugfs active
> operation has ended at that point, but the worker still executes module
> text and manipulates enable_6lowpan and listen_chan.
> 
> bt_6lowpan_exit() removes the debugfs files and immediately closes and
> puts listen_chan. It has no pointer to the queued work item, so it cannot
> cancel or flush it before tearing down the state that the worker uses.
> 
> [...]

Here is the summary with links:
  - Bluetooth: 6lowpan: avoid untracked enable work
    https://git.kernel.org/bluetooth/bluetooth-next/c/a8fb0c8ec7d6

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-06-26 11:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23 16:12 [PATCH] Bluetooth: 6lowpan: avoid untracked enable work Cen Zhang
2026-06-23 17:56 ` bluez.test.bot
2026-06-26 11:16 ` 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=178247260405.3816447.9539369733535711581.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=baijiaju1990@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=zzzccc427@gmail.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.