From: Takashi Iwai <tiwai@suse.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
Clemens Ladisch <clemens@ladisch.de>,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
stable <stable@kernel.org>
Subject: Re: [PATCH] ALSA: fireworks: bound device-supplied status before string array lookup
Date: Fri, 10 Apr 2026 08:23:03 +0200 [thread overview]
Message-ID: <87wlyfgwqg.wl-tiwai@suse.de> (raw)
In-Reply-To: <2026040953-astute-camera-1aa1@gregkh>
On Thu, 09 Apr 2026 16:05:54 +0200,
Greg Kroah-Hartman wrote:
>
> The status field in an EFW response is a 32-bit value supplied by the
> firewire device. efr_status_names[] has 17 entries so a status value
> outside that range goes off into the weeds when looking at the %s value.
>
> Even worse, the status could return EFR_STATUS_INCOMPLETE which is
> 0x80000000, and is obviously not in that array of potential strings.
>
> Fix this up by properly bounding the index against the array size and
> printing "unknown" if it's not recognized.
>
> Cc: Clemens Ladisch <clemens@ladisch.de>
> Cc: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> Cc: Jaroslav Kysela <perex@perex.cz>
> Cc: Takashi Iwai <tiwai@suse.com>
> Fixes: bde8a8f23bbe ("ALSA: fireworks: Add transaction and some commands")
> Cc: stable <stable@kernel.org>
> Assisted-by: gregkh_clanker_t1000
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Applied now to for-next branch. Thanks.
Takashi
prev parent reply other threads:[~2026-04-10 6:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 14:05 [PATCH] ALSA: fireworks: bound device-supplied status before string array lookup Greg Kroah-Hartman
2026-04-09 22:54 ` Takashi Sakamoto
2026-04-10 6:23 ` Takashi Iwai [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=87wlyfgwqg.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=clemens@ladisch.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=o-takashi@sakamocchi.jp \
--cc=perex@perex.cz \
--cc=stable@kernel.org \
--cc=tiwai@suse.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