All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Iaroslav Voitovych <yaroslav.voytovych@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
	luiz.dentz@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: MGMT: Fix status of pending commands flushed on power off
Date: Tue, 29 Sep 2026 15:40:07 +0000	[thread overview]
Message-ID: <179069640730.997963.2754170739187086814.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260924171158.804136-1-yaroslav.voytovych@gmail.com>

Hello:

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

On Thu, 24 Sep 2026 19:11:58 +0200 you wrote:
> cmd_complete_rsp() receives a struct cmd_lookup and, for a pending
> command that has no cmd_complete callback, falls through to
> cmd_status_rsp(cmd, data). cmd_status_rsp() reads data as a u8 *, so
> the status sent comes from the first byte of match->sk's
> representation, not from match->mgmt_status.
> 
> commit f53e1c9c726d ("Bluetooth: MGMT: Fix possible crash on
> mgmt_index_removed") changed the callers' data from &status to &match
> and updated the cmd_complete branch to match->mgmt_status, but left
> the fall-through passing data unchanged.
> 
> [...]

Here is the summary with links:
  - Bluetooth: MGMT: Fix status of pending commands flushed on power off
    https://git.kernel.org/bluetooth/bluetooth-next/c/86ef0f58bdec

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-09-29 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 17:11 [PATCH] Bluetooth: MGMT: Fix status of pending commands flushed on power off Iaroslav Voitovych
2026-09-24 19:32 ` bluez.test.bot
2026-09-29 15:40 ` 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=179069640730.997963.2754170739187086814.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=yaroslav.voytovych@gmail.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.