From: Takashi Iwai <tiwai@suse.de>
To: "Colin King" <colin.king@canonical.com>
Cc: <alsa-devel@alsa-project.org>, "Jaroslav Kysela" <perex@perex.cz>,
<kernel-janitors@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA: cs4236: fix return check from call to pnp_port_start
Date: Thu, 11 Oct 2018 17:42:48 +0200 [thread overview]
Message-ID: <s5hd0sgfq13.wl-tiwai@suse.de> (raw)
In-Reply-To: <20181010141542.16100-1-colin.king@canonical.com>
On Wed, 10 Oct 2018 16:15:42 +0200,
Colin King wrote:
>
> From: Colin Ian King <colin.king@canonical.com>
>
> Currently the return from pnp_port_start is being checked for validity
> by checking if it is greater or equal to zero, however, the return
> is unsigned and hence this check is always true. An 0 return from
> pnp_port_start is actually an error, so fix the check by checking
> for validity when it is non-zero.
I guess you're confused between mpu_port[] and mpu_irq[]?
The check "mpu_irq[] >= 0" here is to see the module parameter value
from user.
thanks,
Takashi
> Detected by CoverityScan, CID#1468334 ("Unsigned compared to 0")
>
> Fixes: a9824c868a2c ("[ALSA] Add CS4232 PnP BIOS support")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> sound/isa/cs423x/cs4236.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/isa/cs423x/cs4236.c b/sound/isa/cs423x/cs4236.c
> index 70559e59d18f..2211c39d2c18 100644
> --- a/sound/isa/cs423x/cs4236.c
> +++ b/sound/isa/cs423x/cs4236.c
> @@ -292,7 +292,7 @@ static int snd_cs423x_pnp_init_mpu(int dev, struct pnp_dev *pdev)
> mpu_irq[dev] = SNDRV_AUTO_IRQ;
> } else {
> mpu_port[dev] = pnp_port_start(pdev, 0);
> - if (mpu_irq[dev] >= 0 &&
> + if (!mpu_irq[dev] &&
> pnp_irq_valid(pdev, 0) && pnp_irq(pdev, 0) >= 0) {
> mpu_irq[dev] = pnp_irq(pdev, 0);
> } else {
> --
> 2.17.1
>
>
next prev parent reply other threads:[~2018-10-11 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 14:15 Colin King
2018-10-11 15:42 ` Takashi Iwai [this message]
2018-10-11 15:47 ` Colin Ian King
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=s5hd0sgfq13.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
/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®