From: patchwork-bot+bluetooth@kernel.org
To: Ying Hsu <yinghsu@chromium.org>
Cc: linux-bluetooth@vger.kernel.org,
chromeos-bluetooth-upstreaming@chromium.org,
johan.hedberg@gmail.com, luiz.dentz@gmail.com,
marcel@holtmann.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Fix hci_suspend_sync crash
Date: Thu, 13 Jul 2023 20:10:22 +0000 [thread overview]
Message-ID: <168927902200.26469.6694434190230470998.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230705210647.1.I636c21e4dc8fe3352f4d7aef26c0ec3857e24ca0@changeid>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 5 Jul 2023 21:06:47 +0000 you wrote:
> If hci_unregister_dev() frees the hci_dev object but hci_suspend_notifier
> may still be accessing it, it can cause the program to crash.
> Here's the call trace:
> <4>[102152.653246] Call Trace:
> <4>[102152.653254] hci_suspend_sync+0x109/0x301 [bluetooth]
> <4>[102152.653259] hci_suspend_dev+0x78/0xcd [bluetooth]
> <4>[102152.653263] hci_suspend_notifier+0x42/0x7a [bluetooth]
> <4>[102152.653268] notifier_call_chain+0x43/0x6b
> <4>[102152.653271] __blocking_notifier_call_chain+0x48/0x69
> <4>[102152.653273] __pm_notifier_call_chain+0x22/0x39
> <4>[102152.653276] pm_suspend+0x287/0x57c
> <4>[102152.653278] state_store+0xae/0xe5
> <4>[102152.653281] kernfs_fop_write+0x109/0x173
> <4>[102152.653284] __vfs_write+0x16f/0x1a2
> <4>[102152.653287] ? selinux_file_permission+0xca/0x16f
> <4>[102152.653289] ? security_file_permission+0x36/0x109
> <4>[102152.653291] vfs_write+0x114/0x21d
> <4>[102152.653293] __x64_sys_write+0x7b/0xdb
> <4>[102152.653296] do_syscall_64+0x59/0x194
> <4>[102152.653299] entry_SYSCALL_64_after_hwframe+0x5c/0xc1
>
> [...]
Here is the summary with links:
- Bluetooth: Fix hci_suspend_sync crash
https://git.kernel.org/bluetooth/bluetooth-next/c/0c9bf63ad8ca
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:[~2023-07-13 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 21:06 [PATCH] Bluetooth: Fix hci_suspend_sync crash Ying Hsu
2023-07-05 21:41 ` bluez.test.bot
2023-07-13 20:10 ` 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=168927902200.26469.6694434190230470998.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=yinghsu@chromium.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;
as well as URLs for NNTP newsgroup(s).