From: Will Cassella <cassew@chromium.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] libavformat/riffec: Zero-initialize `channels` in `ff_get_wav_header`
Date: Tue, 20 Sep 2022 14:52:46 -0700
Message-ID: <CA+F=P4hgWT3ZCBb=9zaD8LN0fFY1ECRfhyxuSThTYiSz7NYY1Q@mail.gmail.com> (raw)
In-Reply-To: <CA+F=P4jBUBywK-XkknshVRZphP1XWGC5axivdgS-=xcySHr3yQ@mail.gmail.com>
Pinging on this!
On Fri, Sep 9, 2022 at 3:50 PM Will Cassella <cassew@chromium.org> wrote:
>
> Clang's static analyzer complains that leaving the `channels` variable
> uninitialized could lead to a code path where the uninitialized value is
> written to `par->ch_layout.nb_channels` at the end of this function.
> This patch simply zero-initializes that variable to avoid that.
>
> Signed-off-by: Will Cassella <cassew@google.com>
> ---
> libavformat/riffdec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavformat/riffdec.c b/libavformat/riffdec.c
> index 3946ecb72f..fc75500d1f 100644
> --- a/libavformat/riffdec.c
> +++ b/libavformat/riffdec.c
> @@ -94,7 +94,7 @@ static void parse_waveformatex(AVFormatContext *s,
> AVIOContext *pb, AVCodecParam
> int ff_get_wav_header(AVFormatContext *s, AVIOContext *pb,
> AVCodecParameters *par, int size, int big_endian)
> {
> - int id, channels;
> + int id, channels = 0;
> uint64_t bitrate = 0;
>
> if (size < 14) {
> --
> 2.37.2.789.g6183377224-goog
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-09-20 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 22:50 Will Cassella
2022-09-20 21:52 ` Will Cassella [this message]
2022-09-20 22:00 ` James Almer
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='CA+F=P4hgWT3ZCBb=9zaD8LN0fFY1ECRfhyxuSThTYiSz7NYY1Q@mail.gmail.com' \
--to=cassew@chromium.org \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git