From: Philipp Stanner <phasta@mailbox.org>
To: Haotian Zhang <vulab@iscas.ac.cn>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: Philipp Stanner <phasta@kernel.org>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: au88x0: Fix incorrect error handling for PCI config reads
Date: Mon, 17 Nov 2025 08:04:16 +0100 [thread overview]
Message-ID: <08327c56d28c0629676ab8120b1eefce9e988676.camel@mailbox.org> (raw)
In-Reply-To: <20251117065559.1138-1-vulab@iscas.ac.cn>
On Mon, 2025-11-17 at 14:55 +0800, Haotian Zhang wrote:
> __snd_vortex_probe() uses pci_read_config_word() that returns PCIBIOS_*
> codes (positive values on error). However, the function checks 'err < 0'
> which can never be true for PCIBIOS_* codes, causing errors to be silently
> ignored.
>
> Check for non-zero return value and convert PCIBIOS_* codes using
> pcibios_err_to_errno() into normal errno before returning them.
>
> Signed-off-by: Haotian Zhang <vulab@iscas.ac.cn>
Reviewed-by: Philipp Stanner <phasta@kernel.org>
> ---
> sound/pci/au88x0/au88x0.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/sound/pci/au88x0/au88x0.c b/sound/pci/au88x0/au88x0.c
> index de56e83d8e10..bb02945793f0 100644
> --- a/sound/pci/au88x0/au88x0.c
> +++ b/sound/pci/au88x0/au88x0.c
> @@ -280,11 +280,11 @@ __snd_vortex_probe(struct pci_dev *pci, const struct pci_device_id *pci_id)
>
> // (5)
> err = pci_read_config_word(pci, PCI_DEVICE_ID, &chip->device);
> - if (err < 0)
> - return err;
> + if (err)
> + return pcibios_err_to_errno(err);
> err = pci_read_config_word(pci, PCI_VENDOR_ID, &chip->vendor);
> - if (err < 0)
> - return err;
> + if (err)
> + return pcibios_err_to_errno(err);
> chip->rev = pci->revision;
> #ifdef CHIP_AU8830
> if ((chip->rev) != 0xfe && (chip->rev) != 0xfa) {
next prev parent reply other threads:[~2025-11-17 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 6:55 Haotian Zhang
2025-11-17 7:04 ` Philipp Stanner [this message]
2025-11-17 16:24 ` Takashi Iwai
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=08327c56d28c0629676ab8120b1eefce9e988676.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=phasta@kernel.org \
--cc=tiwai@suse.com \
--cc=vulab@iscas.ac.cn \
/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
all inboxes | Powered by JetHome®