From: patchwork-bot+bluetooth@kernel.org
To: None <ziniu.wang_1@nxp.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
amitkumar.karwar@nxp.com, rohit.fule@nxp.com,
neeraj.sanjaykale@nxp.com, sherry.sun@nxp.com,
haibo.chen@nxp.com, jun.li@nxp.com, guillaume.legoupil@nxp.com,
salim.chebbo@nxp.com, imx@lists.linux.dev
Subject: Re: [PATCH] Bluetooth: btnxpuart: Shutdown timer and prevent rearming when driver unloading
Date: Fri, 17 May 2024 14:40:33 +0000 [thread overview]
Message-ID: <171595683378.30517.9280094714253637646.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240517111535.856723-1-ziniu.wang_1@nxp.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 17 May 2024 19:15:35 +0800 you wrote:
> From: Luke Wang <ziniu.wang_1@nxp.com>
>
> When unload the btnxpuart driver, its associated timer will be deleted.
> If the timer happens to be modified at this moment, it leads to the
> kernel call this timer even after the driver unloaded, resulting in
> kernel panic.
> Use timer_shutdown_sync() instead of del_timer_sync() to prevent rearming.
>
> [...]
Here is the summary with links:
- Bluetooth: btnxpuart: Shutdown timer and prevent rearming when driver unloading
https://git.kernel.org/bluetooth/bluetooth-next/c/3afc41cbec84
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-05-17 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 11:15 [PATCH] Bluetooth: btnxpuart: Shutdown timer and prevent rearming when driver unloading ziniu.wang_1
2024-05-17 11:57 ` bluez.test.bot
2024-05-17 14:40 ` patchwork-bot+bluetooth [this message]
2024-05-27 7:15 ` [PATCH] " Bough Chen
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=171595683378.30517.9280094714253637646.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=amitkumar.karwar@nxp.com \
--cc=guillaume.legoupil@nxp.com \
--cc=haibo.chen@nxp.com \
--cc=imx@lists.linux.dev \
--cc=jun.li@nxp.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=neeraj.sanjaykale@nxp.com \
--cc=rohit.fule@nxp.com \
--cc=salim.chebbo@nxp.com \
--cc=sherry.sun@nxp.com \
--cc=ziniu.wang_1@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox