From: patchwork-bot+bluetooth@kernel.org
To: Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>
Cc: linux-bluetooth@vger.kernel.org, linux-pci@vger.kernel.org,
bhelgaas@google.com, ravishankar.srivatsa@intel.com,
chethan.tumkur.narayan@intel.com
Subject: Re: [PATCH v1] Bluetooth: btintel_pcie: Fix null pointer dereference in remove
Date: Mon, 01 Jun 2026 19:10:08 +0000 [thread overview]
Message-ID: <178034100838.57646.11704665987158144101.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260601102612.2164388-1-chandrashekar.devegowda@intel.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 1 Jun 2026 15:56:11 +0530 you wrote:
> Add a NULL check for pci_get_drvdata() in btintel_pcie_remove() to
> prevent a null pointer dereference. This can occur when
> btintel_pcie_remove() is called concurrently from the PLDR
> device_reprobe path on another CPU, after pci_set_drvdata(pdev, NULL)
> has already been executed.
>
> Fixes: 8c0693e29dba ("Bluetooth: btintel_pcie: Support Product level reset")
> Signed-off-by: Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: btintel_pcie: Fix null pointer dereference in remove
https://git.kernel.org/bluetooth/bluetooth-next/c/2bf22888ea6d
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:[~2026-06-01 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 10:26 [PATCH v1] Bluetooth: btintel_pcie: Fix null pointer dereference in remove Chandrashekar Devegowda
2026-06-01 12:47 ` [v1] " bluez.test.bot
2026-06-01 19: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=178034100838.57646.11704665987158144101.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=bhelgaas@google.com \
--cc=chandrashekar.devegowda@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=ravishankar.srivatsa@intel.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