From: Marton Balint <cus@passwd.hu> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 3/3] avformat/hlsenc: Fix path handling for Windows Date: Sat, 14 Jun 2025 17:34:56 +0200 (CEST) Message-ID: <4b6d8494-2cfe-e118-516d-4ed9c94b757e@passwd.hu> (raw) In-Reply-To: <DM8P223MB03655694F81E3BE9754E6763BA77A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> On Fri, 13 Jun 2025, softworkz . wrote: > > >> -----Original Message----- >> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of >> Marton Balint >> Sent: Freitag, 13. Juni 2025 23:36 >> To: FFmpeg development discussions and patches <ffmpeg- >> devel@ffmpeg.org> >> Subject: Re: [FFmpeg-devel] [PATCH 3/3] avformat/hlsenc: Fix path >> handling for Windows >> >> >> >> On Fri, 13 Jun 2025, softworkz wrote: >> >>> From: softworkz <softworkz@hotmail.com> >>> >> >> Can you give an example where the path handling is wrong and where >> this >> patch fixes it? > > c:\hls\video1\master.m3u8 What I meant is that you should try to explain "fix" better in the commit message, like: When base_output_dirname was determined only '/' was searched for as path separator. get_relative_url() on the other hand searched for both forward and backward slash regardless of OS. Fix these issues by factorizing the separator finder function, only search for backslash for Windows/DOS and use that in both places. > > > >> Is there a trac ticket? > > Good question, there well may be. > Its worth doing a quick search, if there is one you might want to reference it in the commit message. > > >> >>> Signed-off-by: softworkz <softworkz@hotmail.com> >>> --- >>> libavformat/hlsenc.c | 43 ++++++++++++++++++++++++++++----------- >> ---- >>> 1 file changed, 28 insertions(+), 15 deletions(-) >>> >>> diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c >>> index f81385d0b4..ba1e74e999 100644 >>> --- a/libavformat/hlsenc.c >>> +++ b/libavformat/hlsenc.c >>> @@ -329,6 +329,23 @@ static int hlsenc_io_close(AVFormatContext >> *s, AVIOContext **pb, char *filename) >>> return ret; >>> } >>> >>> +static int get_last_separator_pos(const char *path) >> >> size_t > > Cannot return -1. Indeed, actually ptrdiff_t would be the proper type. > > >>> +{ >>> + if (!path || *path == '\0') >>> + return -1; >>> + >>> + char *p = strrchr(path, '/'); >>> +#if HAVE_DOS_PATHS >>> + char *q = strrchr(path, '\\'); >>> + p = FFMAX(p, q); >> >> You are comparing potentially NULL pointers here. > > > It's the same like in av_basename() or av_dirname() And those are likely wrong too. > > > >>> +#endif >>> + >>> + if (!p) >>> + return -1; >>> + >>> + return p - path; >>> +} >>> + >>> static void set_http_options(AVFormatContext *s, AVDictionary >> **options, HLSContext *c) >>> { >>> int http_base_proto = ff_is_http_proto(s->url); >>> @@ -1408,14 +1425,10 @@ static int >> hls_rename_temp_file(AVFormatContext *s, AVFormatContext *oc) >>> >>> static const char* get_relative_url(const char *master_url, const >> char *media_url) >>> { >>> - const char *p = strrchr(master_url, '/'); >>> - size_t base_len = 0; >>> - >>> - if (!p) p = strrchr(master_url, '\\'); >>> + int pos = get_last_separator_pos(master_url); >> >> size_t, and you can keep using base_len variable, you don't have to >> rename, it is used for the same purpose as before. > > >> >>> >>> - if (p) { >>> - base_len = p - master_url; >>> - if (av_strncasecmp(master_url, media_url, base_len)) { >>> + if (pos >= 0) { > > That's the check for not being -1 > > int64_t should cover the whole range - can I use that instead? ptrdiff_t. Thanks, Marton _______________________________________________ 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-14 15:38 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-13 17:19 [FFmpeg-devel] [PATCH 0/3] avformat/hlsenc: Some HLS improvements ffmpegagent 2025-06-13 17:19 ` [FFmpeg-devel] [PATCH 1/3] avformat/hlsenc: Log information about segments written softworkz 2025-06-13 21:02 ` Marton Balint 2025-06-13 23:31 ` softworkz . 2025-06-13 17:19 ` [FFmpeg-devel] [PATCH 2/3] avformat/hlsenc: Log InitFileComplete message softworkz 2025-06-13 17:19 ` [FFmpeg-devel] [PATCH 3/3] avformat/hlsenc: Fix path handling for Windows softworkz 2025-06-13 21:36 ` Marton Balint 2025-06-13 23:34 ` softworkz . 2025-06-14 15:34 ` Marton Balint [this message] 2025-06-14 0:56 ` softworkz . 2025-06-14 0:12 ` [FFmpeg-devel] [PATCH v2] " softworkz
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=4b6d8494-2cfe-e118-516d-4ed9c94b757e@passwd.hu \ --to=cus@passwd.hu \ --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