Linux bluetooth development
 help / color / mirror / Atom feed
From: Ameen Al-Asady <ameenaladdin@gmail.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: linux-bluetooth@vger.kernel.org,
	Marcel Holtmann <marcel@holtmann.org>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Subject: Re: [PATCH 1/2] Bluetooth: btintel: Fix spurious error on FW download error recovery
Date: Mon, 13 Jul 2026 20:09:49 -0700 (PDT)	[thread overview]
Message-ID: <6a55a87d.c6960a0e.13e016.2f67@mx.google.com> (raw)
In-Reply-To: <0f0d783d-8b03-4048-bd7f-b97dc2bce92f@molgen.mpg.de>

Hi Paul,

Thanks for the review.

> "fail" is ambiguous to me. Maybe "errors out".

Reworded in v2.

> Any hint how to match the firmware versions, or add a sentence what
> firmware is on the controller and which one is downloaded?

Added the firmware build lines to the log excerpt in v2. The
controller was running build 81755 (2024.33) and the file on disk
contained build 82122 (2026.5).

> Please mention the system you tested this on.

Done. Tested on an Intel AX210 (USB 8087:0032) on a 7.1.3 kernel by
rebinding btusb with a non-matching firmware file on disk, in both
the downgrade and upgrade direction. Both runs took the -ENODEV path,
logged the info message instead of the error and completed the
download after re-enumeration.

> Excuse my ignorance, but moving kfree_skb to a new else branch is
> not totally clear to me.

When __hci_cmd_sync() fails it returns an error pointer instead of a
real skb, so there is nothing to free. kfree_skb() must only run in
the success case, which is now the else branch. The old code had the
same behavior through the early return.

v2 sent.

Regards,
Ameen

      reply	other threads:[~2026-07-14  3:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 21:55 [PATCH 1/2] Bluetooth: btintel: Fix spurious error on FW download error recovery Ameen Al-Asady
2026-07-13 21:55 ` [PATCH 2/2] Bluetooth: hci_sync: Skip MSFT/AOSP init when controller init failed Ameen Al-Asady
2026-07-13 22:50 ` [1/2] Bluetooth: btintel: Fix spurious error on FW download error recovery bluez.test.bot
2026-07-14  0:00 ` [PATCH 1/2] " Paul Menzel
2026-07-14  3:09   ` Ameen Al-Asady [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=6a55a87d.c6960a0e.13e016.2f67@mx.google.com \
    --to=ameenaladdin@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=pmenzel@molgen.mpg.de \
    /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