From: Takashi Iwai <tiwai@suse.de>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Jaroslav Kysela" <perex@perex.cz>, <alsa-devel@alsa-project.org>,
<linux-mips@linux-mips.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA: mips: avoid potential uninitialized variable use
Date: Mon, 16 Jan 2017 13:28:56 +0100 [thread overview]
Message-ID: <s5hd1fnxk6v.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170116110517.3833976-1-arnd@arndb.de>
On Mon, 16 Jan 2017 12:04:56 +0100,
Arnd Bergmann wrote:
>
> MIPS allmodconfig results in this warning:
>
> sound/mips/hal2.c: In function 'hal2_gain_get':
> sound/mips/hal2.c:224:35: error: 'r' may be used uninitialized in this function [-Werror=maybe-uninitialized]
> sound/mips/hal2.c:223:35: error: 'l' may be used uninitialized in this function [-Werror=maybe-uninitialized]
> sound/mips/hal2.c: In function 'hal2_gain_put':
> sound/mips/hal2.c:260:13: error: 'new' may be used uninitialized in this function [-Werror=maybe-uninitialized]
> sound/mips/hal2.c:260:13: error: 'old' may be used uninitialized in this function [-Werror=maybe-uninitialized]
>
> It's easy enough to avoid by adding a 'default' clause to the switch
> statements here. I assume that in practice no other case can happen,
> but adding a default puts us on the safe side and shuts up the warnings.
Well, these cases are logical errors that must not happen, so
returning an error would be a "safer", IMO.
thanks,
Takashi
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> sound/mips/hal2.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/sound/mips/hal2.c b/sound/mips/hal2.c
> index ede449f0b50d..0af4f7a9b3e7 100644
> --- a/sound/mips/hal2.c
> +++ b/sound/mips/hal2.c
> @@ -219,6 +219,9 @@ static int hal2_gain_get(struct snd_kcontrol *kcontrol,
> l = (tmp >> H2I_C2_L_GAIN_SHIFT) & 15;
> r = (tmp >> H2I_C2_R_GAIN_SHIFT) & 15;
> break;
> + default:
> + l = 0;
> + r = 0;
> }
> ucontrol->value.integer.value[0] = l;
> ucontrol->value.integer.value[1] = r;
> @@ -256,6 +259,9 @@ static int hal2_gain_put(struct snd_kcontrol *kcontrol,
> new |= (r << H2I_C2_R_GAIN_SHIFT);
> hal2_i_write32(hal2, H2I_ADC_C2, new);
> break;
> + default:
> + new = 0;
> + old = 0;
> }
> return old != new;
> }
> --
> 2.9.0
>
>
next prev parent reply other threads:[~2017-01-16 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 11:04 Arnd Bergmann
2017-01-16 12:28 ` Takashi Iwai [this message]
2017-01-16 13:26 ` Arnd Bergmann
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=s5hd1fnxk6v.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.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®