From: Takashi Iwai <tiwai@suse.de>
To: Aiswarya Cyriac <Aiswarya.Cyriac@opensynergy.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"perex@perex.cz" <perex@perex.cz>,
"tiwai@suse.com" <tiwai@suse.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
Anton Yakovlev <Anton.Yakovlev@opensynergy.com>,
coverity-bot <keescook+coverity-bot@chromium.org>,
Mikhail Golubev-Ciuchea <Mikhail.Golubev-Ciuchea@opensynergy.com>
Subject: Re: [PATCH] ALSA: virtio: Fix "Coverity: virtsnd_kctl_tlv_op(): Uninitialized variables" warning.
Date: Wed, 14 Feb 2024 14:16:45 +0100 [thread overview]
Message-ID: <87v86rgp8i.wl-tiwai@suse.de> (raw)
In-Reply-To: <FR3P281MB2527A0498C3B1E3899087028E64E2@FR3P281MB2527.DEUP281.PROD.OUTLOOK.COM>
On Wed, 14 Feb 2024 14:07:40 +0100,
Aiswarya Cyriac wrote:
>
>
> On Wed, 14 Feb 2024 12:30:19 +0100,
> Michael S. Tsirkin wrote:
> >>
> >> On Wed, Feb 14, 2024 at 09:08:26AM +0000, Aiswarya Cyriac wrote:
> >> > Hi Michael,
> >> >
> >> > Thank you for reviewing. I have updated my response inline
> >> >
> >> > On Tue, Feb 13, 2024 at 09:51:30AM +0100, Aiswarya Cyriac wrote:
> >> > >> Fix the following warning when building virtio_snd driver.
> >> > >>
> >> > >> "
> >> > >> *** CID 1583619: Uninitialized variables (UNINIT)
> >> > >> sound/virtio/virtio_kctl.c:294 in virtsnd_kctl_tlv_op()
> >> > >> 288
> >> > >> 289 break;
> >> > >> 290 }
> >> > >> 291
> >> > >> 292 kfree(tlv);
> >> > >> 293
> >> > >> vvv CID 1583619: Uninitialized variables (UNINIT)
> >> > >> vvv Using uninitialized value "rc".
> >> > >> 294 return rc;
> >> > >> 295 }
> >> > >> 296
> >> > >> 297 /**
> >> > >> 298 * virtsnd_kctl_get_enum_items() - Query items for the ENUMERATED element type.
> >> > >> 299 * @snd: VirtIO sound device.
> >> > >> "
> >> > >>
> >> > >> Signed-off-by: Anton Yakovlev <anton.yakovlev@opensynergy.com>
> >> > >> Signed-off-by: Aiswarya Cyriac <aiswarya.cyriac@opensynergy.com>
> >> > >> Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
> >> > >> Addresses-Coverity-ID: 1583619 ("Uninitialized variables")
> >> > >> Fixes: d6568e3de42d ("ALSA: virtio: add support for audio controls")
> >> >
> >> > >I don't know enough about ALSA to say whether the patch is correct. But
> >> > >the commit log needs work: please, do not "fix warnings" - analyse the
> >> > >code and explain whether there is a real issue and if yes what is it
> >> > >and how it can trigger. Is an invalid op_flag ever passed?
> >> > >If it's just a coverity false positive it might be ok to
> >> > >work around that but document this.
> >> >
> >> > This warning is caused by the absence of the "default" branch in the
> >> > switch-block, and is a false positive because the kernel calls
> >> > virtsnd_kctl_tlv_op() only with values for op_flag processed in
> >> > this block.
> >>
> >> Well we don't normally have functions validate inputs.
> >> In this case I am not really sure we should bother
> >> with adding dead code. If you really want to, add BUG_ON.
>
> > Please don't use BUG_ON() in such a case...
> > There is no reason to break the whole operation.
>
> How about adding a WARN_ON() on default case?
That's better :)
thanks,
Takashi
prev parent reply other threads:[~2024-02-14 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 8:51 [PATCH] ALSA: virtio: Fix "Coverity: virtsnd_kctl_tlv_op(): Uninitialized variables" warning Aiswarya Cyriac
2024-02-13 9:02 ` Takashi Iwai
2024-02-13 9:07 ` Michael S. Tsirkin
2024-02-13 9:42 ` Takashi Iwai
2024-02-13 9:06 ` Michael S. Tsirkin
2024-02-14 9:08 ` Aiswarya Cyriac
2024-02-14 11:30 ` Michael S. Tsirkin
2024-02-14 11:37 ` Takashi Iwai
2024-02-14 13:07 ` Aiswarya Cyriac
2024-02-14 13:16 ` 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=87v86rgp8i.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Aiswarya.Cyriac@opensynergy.com \
--cc=Anton.Yakovlev@opensynergy.com \
--cc=Mikhail.Golubev-Ciuchea@opensynergy.com \
--cc=alsa-devel@alsa-project.org \
--cc=jasowang@redhat.com \
--cc=keescook+coverity-bot@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).