From: patchwork-bot+bluetooth@kernel.org
To: Francesco Dolcini <francesco@dolcini.it>
Cc: amitkumar.karwar@nxp.com, neeraj.sanjaykale@nxp.com,
marcel@holtmann.org, luiz.dentz@gmail.com,
marcel.ziswiler@toradex.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
francesco.dolcini@toradex.com
Subject: Re: [PATCH v2] Bluetooth: btnxpuart: Fix btnxpuart_close
Date: Mon, 04 Mar 2024 21:30:27 +0000 [thread overview]
Message-ID: <170958782727.29902.5588082329084966658.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240304181421.14777-1-francesco@dolcini.it>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 4 Mar 2024 19:14:21 +0100 you wrote:
> From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>
> Fix scheduling while atomic BUG in btnxpuart_close(), properly
> purge the transmit queue and free the receive skb.
>
> [ 10.973809] BUG: scheduling while atomic: kworker/u9:0/80/0x00000002
> ...
> [ 10.980740] CPU: 3 PID: 80 Comm: kworker/u9:0 Not tainted 6.8.0-rc7-0.0.0-devel-00005-g61fdfceacf09 #1
> [ 10.980751] Hardware name: Toradex Verdin AM62 WB on Dahlia Board (DT)
> [ 10.980760] Workqueue: hci0 hci_power_off [bluetooth]
> [ 10.981169] Call trace:
> ...
> [ 10.981363] uart_update_mctrl+0x58/0x78
> [ 10.981373] uart_dtr_rts+0x104/0x114
> [ 10.981381] tty_port_shutdown+0xd4/0xdc
> [ 10.981396] tty_port_close+0x40/0xbc
> [ 10.981407] uart_close+0x34/0x9c
> [ 10.981414] ttyport_close+0x50/0x94
> [ 10.981430] serdev_device_close+0x40/0x50
> [ 10.981442] btnxpuart_close+0x24/0x98 [btnxpuart]
> [ 10.981469] hci_dev_close_sync+0x2d8/0x718 [bluetooth]
> [ 10.981728] hci_dev_do_close+0x2c/0x70 [bluetooth]
> [ 10.981862] hci_power_off+0x20/0x64 [bluetooth]
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: btnxpuart: Fix btnxpuart_close
https://git.kernel.org/bluetooth/bluetooth-next/c/3f40a47f3589
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:[~2024-03-04 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 18:14 [PATCH v2] Bluetooth: btnxpuart: Fix btnxpuart_close Francesco Dolcini
2024-03-04 18:57 ` [v2] " bluez.test.bot
2024-03-04 21:30 ` 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=170958782727.29902.5588082329084966658.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=amitkumar.karwar@nxp.com \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel.ziswiler@toradex.com \
--cc=marcel@holtmann.org \
--cc=neeraj.sanjaykale@nxp.com \
--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 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.