All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Kiran K <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
	chethan.tumkur.narayan@intel.com,
	chandrashekar.devegowda@intel.com
Subject: Re: [PATCH v2] Bluetooth: btintel_pcie: serialize reset_type with RECOVERY_IN_PROGRESS
Date: Thu, 16 Jul 2026 15:20:11 +0000	[thread overview]
Message-ID: <178421521189.862995.16187217090027119655.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260715161754.213393-1-kiran.k@intel.com>

Hello:

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

On Wed, 15 Jul 2026 21:47:53 +0530 you wrote:
> The reset path had two concurrency holes. Both are reachable in
> practice when btintel_pcie_hw_error() is invoked from the HCI rx
> path while another reset is being requested or is already in
> flight.
> 
>   1. data->reset_type was a plain shared field. The hw_error path
>      wrote it BEFORE the test_and_set_bit(RECOVERY_IN_PROGRESS)
>      guard inside btintel_pcie_reset(), so a second hw_error could
>      clobber the type chosen by an earlier in-flight request:
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: btintel_pcie: serialize reset_type with RECOVERY_IN_PROGRESS
    https://git.kernel.org/bluetooth/bluetooth-next/c/bd8bee79e1fa

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-07-16 15:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 16:17 [PATCH v2] Bluetooth: btintel_pcie: serialize reset_type with RECOVERY_IN_PROGRESS Kiran K
2026-07-15 17:10 ` [v2] " bluez.test.bot
2026-07-16 15:20 ` 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=178421521189.862995.16187217090027119655.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=chandrashekar.devegowda@intel.com \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=kiran.k@intel.com \
    --cc=linux-bluetooth@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 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.