From: Appaji Chintimi <appaji12368@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v1] fftools/ffplay: Resolve input file path before processing
Date: Fri, 16 May 2025 01:24:52 +0530
Message-ID: <CAGVwuGg+MR2_0wgNgiCjqihxcK1jNkuKMSLjL1D6FLMR+roobA@mail.gmail.com> (raw)
In-Reply-To: <2f7d5924-ebfb-2e00-8573-5a1cb6cdd27b@passwd.hu>
Can you elaborate a bit more why this requires more changes? My
understanding is, to check for different cases and handle them differently:
1. "-" gets replaced with "fd:", and it's passed directly to
"input_filename" without resolving.
2. if the path contains "://", that too gets passed on without resolving it
further (handles http://, https://, ftp:// etc..)
3. Only after these two checks, resolve the "filename" and pass on to
"input_filename".
On Wed, 14 May 2025 at 23:40, Marton Balint <cus@passwd.hu> wrote:
>
>
> On Wed, 14 May 2025, Nicolas George wrote:
>
> > Appaji (HE12025-05-14):
> >> Fixes ticket: https://trac.ffmpeg.org/ticket/11574
> >>
> >> Signed-off-by: Appaji <appaji12368@gmail.com>
> >> ---
> >> fftools/ffplay.c | 13 +++++++++++--
> >> 1 file changed, 11 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/fftools/ffplay.c b/fftools/ffplay.c
> >> index 2a572fc3aa..42f0584b55 100644
> >> --- a/fftools/ffplay.c
> >> +++ b/fftools/ffplay.c
> >> @@ -27,6 +27,7 @@
> >> #include "config_components.h"
> >> #include <math.h>
> >> #include <limits.h>
> >> +#include <stdlib.h>
> >> #include <signal.h>
> >> #include <stdint.h>
> >>
> >> @@ -3623,9 +3624,17 @@ static int opt_input_file(void *optctx, const
> char *filename)
> >> filename, input_filename);
> >> return AVERROR(EINVAL);
> >> }
> >> - if (!strcmp(filename, "-"))
> >> +
> >> + char resolved_path[PATH_MAX];
> >> +
> >> + if (!realpath(filename, resolved_path)) {
> >> + av_log(NULL, AV_LOG_FATAL, "Failed to resolve path for '%s':
> %s\n", filename, strerror(errno));
> >> + return AVERROR(errno);
> >> + }
> >> +
> >
> > Hi. Thanks for the patch. Did you test it with non-filenames arguments,
> > for example http://…?
> >
> >> + if (!strcmp(resolved_path, "-"))
> >> filename = "fd:";
> >
> > This should happen before resolution.
> >
> >> - input_filename = av_strdup(filename);
> >> + input_filename = av_strdup(resolved_path);
> >> if (!input_filename)
> >> return AVERROR(ENOMEM);
> >>
> >
> > On the whole, I think you are going at it wrong: you are only fixing
> > this for ffplay, not for ffprobe, ffmpeg and other applications built on
> > the libraries, and resolving the path can have side effects, for example
> > if you do not have permission on a parent of the current working
> > directory.
> >
> > IMO, the correct way would be to add a stat() early in the opening of
> > the file and test the device number. But that requires changing quite a
> > lot of things.
>
> Agreed. You should improve the probing function to fix the ticket, you can
> do a stat in v4l2_read_probe() in libavdevice/v4l2.c, check if it is a
> char device and try a V4L2 IOCTL on it to make sure it is a V4L2 device.
>
> Regards,
> Marton
>
> >
> > Regards,
> >
> > --
> > Nicolas George
> > _______________________________________________
> > 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".
> _______________________________________________
> 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".
>
_______________________________________________
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-05-15 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 20:58 Appaji
2025-05-14 11:49 ` Nicolas George
2025-05-14 18:06 ` Marton Balint
2025-05-15 19:54 ` Appaji Chintimi [this message]
2025-05-21 5:17 ` Appaji Chintimi
2025-05-21 6:50 ` Nicolas George
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=CAGVwuGg+MR2_0wgNgiCjqihxcK1jNkuKMSLjL1D6FLMR+roobA@mail.gmail.com \
--to=appaji12368@gmail.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