From: Takashi Iwai <tiwai@suse.de>
To: "Alexey V. Vissarionov" <gremlin@altlinux.org>
Cc: alsa-devel@alsa-project.org, lvc-project@linuxtesting.org,
Ian Minett <ian_minett@creativelabs.com>,
ye xingchen <ye.xingchen@zte.com.cn>,
Takashi Iwai <tiwai@suse.com>, Xian Wang <dev@xianwang.io>
Subject: Re: [PATCH] ALSA: hda/ca0132: minor fix for allocation size
Date: Tue, 17 Jan 2023 18:02:50 +0100 [thread overview]
Message-ID: <87zgah5c1x.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230117111522.GA15213@altlinux.org>
On Tue, 17 Jan 2023 12:15:23 +0100,
Alexey V. Vissarionov wrote:
>
> Although the "dma_chan" pointer occupies more or equal space compared
> to "*dma_chan", the allocation size should use the size of variable
> itself.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Fixes: 01ef7dbffb411d9d ("ALSA: hda - Update CA0132 codec to load DSP firmware binary")
> Signed-off-by: Alexey V. Vissarionov <gremlin@altlinux.org>
Thanks, applied now.
(BTW, the Fixes tag should have the commit ID in 12 chars. I
corrected locally.)
Takashi
prev parent reply other threads:[~2023-01-17 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 11:15 [PATCH] ALSA: hda/ca0132: minor fix for allocation size Alexey V. Vissarionov
2023-01-17 17: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=87zgah5c1x.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=dev@xianwang.io \
--cc=gremlin@altlinux.org \
--cc=ian_minett@creativelabs.com \
--cc=lvc-project@linuxtesting.org \
--cc=tiwai@suse.com \
--cc=ye.xingchen@zte.com.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