From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 01/11] fftools/graph/graphprint: Fix races when initializing graphprint Date: Sun, 1 Jun 2025 12:39:46 +0200 Message-ID: <GV1P250MB0737060CAFC7C58F92867B668F63A@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> (raw) In-Reply-To: <DM8P223MB0365E33706214E45CD464A99BA63A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> softworkz .: > > >> -----Original Message----- >> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Andreas >> Rheinhardt >> Sent: Sonntag, 1. Juni 2025 05:27 >> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> >> Subject: [FFmpeg-devel] [PATCH 01/11] fftools/graph/graphprint: Fix races when >> initializing graphprint >> >> Patches attached. >> >> - Andreas > > > Hi Andreas,, > > thanks for the patches - most looking good from a glance. > > I have a few questions: > > - Why do you want to remove the ResourceManager AVClass? Because I think callers should provide their own logcontext, instead of adding yet another AVClass that is likely never used. > It wasn't unused. Now the prefix is gone for log entries in > decompress_gzip() True, this patch is just wrong (in case of decompression errors, av_log() will treat ResourceManagerContext as a logging context, although it is no more; this would lead to segfaults if AVDictionary is already set, i.e. when initializing the second resource). > Actually, all av_log() calls should include the resman_ctx > Seems this has been forgotten (well..by me) > > - For the registered_formatters initialization: > I used to have initialization order issues when I had tried > with static initialization. That's the reason for those functions > Probably you've done it differently as it seems to work so far What issues? > > - In resman.c:64 - should the resman_ctx be static? Yes, of course. Will change it in the patch. Also notice that patch #1 needs to be fixed, too (it failed when actual options were passed). Will send an updated version soon. - Andreas _______________________________________________ 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:[~2025-06-01 10:39 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-01 3:27 Andreas Rheinhardt 2025-06-01 4:19 ` softworkz . 2025-06-01 10:39 ` Andreas Rheinhardt [this message] 2025-06-01 21:41 ` softworkz . 2025-06-01 22:07 ` Andreas Rheinhardt 2025-06-01 23:14 ` softworkz . 2025-06-01 11:25 ` Andreas Rheinhardt
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=GV1P250MB0737060CAFC7C58F92867B668F63A@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM \ --to=andreas.rheinhardt@outlook.com \ --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