From: Takashi Iwai <tiwai@suse.de>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Jaroslav Kysela" <perex@perex.cz>, <alsa-devel@alsa-project.org>,
"Colin Ian King" <colin.king@canonical.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA: au88x0: avoid theoretical uninitialized access
Date: Fri, 24 Mar 2017 12:02:04 +0100 [thread overview]
Message-ID: <s5hpoh7q6oj.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170323151607.636485-1-arnd@arndb.de>
On Thu, 23 Mar 2017 16:15:55 +0100,
Arnd Bergmann wrote:
>
> The latest gcc-7.0.1 snapshot points out that we if nr_ch is zero, we never
> initialize some variables:
>
> sound/pci/au88x0/au88x0_core.c: In function 'vortex_adb_allocroute':
> sound/pci/au88x0/au88x0_core.c:2304:68: error: 'mix[0]' may be used uninitialized in this function [-Werror=maybe-uninitialized]
> sound/pci/au88x0/au88x0_core.c:2305:58: error: 'src[0]' may be used uninitialized in this function [-Werror=maybe-uninitialized]
>
> I assume this can never happen in practice, but adding a check here doesn't
> hurt either and avoids the warning. The code has been unchanged since
> the start of git history.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Yeah, this shouldn't happen in practice, but better to cover.
I applied the patch now. Thanks.
Takashi
> ---
> sound/pci/au88x0/au88x0_core.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/sound/pci/au88x0/au88x0_core.c b/sound/pci/au88x0/au88x0_core.c
> index e1af24f87566..c308a4f70550 100644
> --- a/sound/pci/au88x0/au88x0_core.c
> +++ b/sound/pci/au88x0/au88x0_core.c
> @@ -2279,6 +2279,9 @@ vortex_adb_allocroute(vortex_t *vortex, int dma, int nr_ch, int dir,
> } else {
> int src[2], mix[2];
>
> + if (nr_ch < 1)
> + return -EINVAL;
> +
> /* Get SRC and MIXER hardware resources. */
> for (i = 0; i < nr_ch; i++) {
> if ((mix[i] =
> --
> 2.9.0
>
prev parent reply other threads:[~2017-03-24 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 15:15 Arnd Bergmann
2017-03-24 11:02 ` 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=s5hpoh7q6oj.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=colin.king@canonical.com \
--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®