Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Zhao Zhili via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "mypopy@gmail.com" <mypopy@gmail.com>,
	Zhao Zhili <quinkblack@foxmail.com>
Subject: [FFmpeg-devel] Re: [PATCH] doc/examples/vaapi_encode: fix invalid check on fwrite (PR #20396)
Date: Wed, 3 Sep 2025 14:45:22 +0800
Message-ID: <tencent_686CE0A45B1635A9809034D53F6757E19C09@qq.com> (raw)
In-Reply-To: <CACYjbn3GctcOxacPK0_z12EcsMkqXUmcV_DnekbSz_eZ92+vCw@mail.gmail.com>



> On Sep 3, 2025, at 11:30, mypopy--- via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote:
> 
> On Tue, Sep 2, 2025 at 6:13 PM Zhao Zhili via ffmpeg-devel
> <ffmpeg-devel@ffmpeg.org <mailto:ffmpeg-devel@ffmpeg.org>> wrote:
>> 
>> PR #20396 opened by Zhao Zhili (quink)
>> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20396
>> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20396.patch
>> 
>> Firstly, the order of the parameters to fwrite was incorrect, which
>> make fwrite always return 1 or 0.
>> 
>> Secondly, enc_pkt->size is 0 after av_packet_unref, which makes
>> the check invalid again.
>> 
>> Fix regression from 3e4bfff2.
>> 
>> Co-Authored-by: Jin Bo <jinbo@loongson.cn>
>> Signed-off-by: Zhao Zhili <zhilizhao@tencent.com>
>> 
>> 
>>> From 5147580520ad627ffbae692119c4e92a7c489c76 Mon Sep 17 00:00:00 2001
>> From: Zhao Zhili <zhilizhao@tencent.com>
>> Date: Tue, 2 Sep 2025 18:04:11 +0800
>> Subject: [PATCH] doc/examples/vaapi_encode: fix invalid check on fwrite
>> 
>> Firstly, the order of the parameters to fwrite was incorrect, which
>> make fwrite always return 1 or 0.
>> 
>> Secondly, enc_pkt->size is 0 after av_packet_unref, which makes
>> the check invalid again.
>> 
>> Fix regression from 3e4bfff2.
>> 
>> Co-Authored-by: Jin Bo <jinbo@loongson.cn>
>> Signed-off-by: Zhao Zhili <zhilizhao@tencent.com>
>> ---
>> doc/examples/vaapi_encode.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>> 
>> diff --git a/doc/examples/vaapi_encode.c b/doc/examples/vaapi_encode.c
>> index ff3ebb1e2b..3d718c4c4f 100644
>> --- a/doc/examples/vaapi_encode.c
>> +++ b/doc/examples/vaapi_encode.c
>> @@ -86,9 +86,10 @@ static int encode_write(AVCodecContext *avctx, AVFrame *frame, FILE *fout)
>>             break;
>> 
>>         enc_pkt->stream_index = 0;
>> -        ret = fwrite(enc_pkt->data, enc_pkt->size, 1, fout);
>> +        int size = enc_pkt->size;
>> +        ret = fwrite(enc_pkt->data, 1, size, fout);
>>         av_packet_unref(enc_pkt);
>> -        if (ret != enc_pkt->size) {
> I think only fixing the part that checks the return value should ok,I
> having looked at the original code, it was simply intended to write a
> single NALU at once.

Fixed by
        if (!ret) {
            ret = AVERROR(errno);
            break;
        }

>> +        if (ret != size) {
>>             ret = AVERROR(errno);
>>             break;
>>         }
>> --
>> 2.49.1
> _______________________________________________
> ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org <mailto:ffmpeg-devel@ffmpeg.org>
> To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org <mailto:ffmpeg-devel-leave@ffmpeg.org>
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2025-09-03  6:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 10:13 [FFmpeg-devel] " Zhao Zhili via ffmpeg-devel
2025-09-03  3:30 ` [FFmpeg-devel] " mypopy--- via ffmpeg-devel
2025-09-03  6:45   ` Zhao Zhili via ffmpeg-devel [this message]
2025-09-03 13:13     ` mypopy--- via ffmpeg-devel

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=tencent_686CE0A45B1635A9809034D53F6757E19C09@qq.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=mypopy@gmail.com \
    --cc=quinkblack@foxmail.com \
    /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