From: Andriy Gelman <andriy.gelman@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] 答复: [PATCH] avcodec/v4l2_m2m: close the invalid file descriptor -1 in function v4l2_m2m_destroy_context
Date: Sat, 25 Jun 2022 18:05:50 -0400
Message-ID: <20220625220550.7dj4zku4lte2atkf@jackie> (raw)
In-Reply-To: <bb49a8cada644e1c95624ccf9cb19b9a@huawei.com>
Hi,
On Sat, 25. Jun 03:04, Wujian(Chin) wrote:
> Hi:
> Please review it.
> Thks!
>
> -----邮件原件-----
> 发件人: Wujian(Chin)
> 发送时间: 2022年6月15日 19:15
> 收件人: 'ffmpeg-devel@ffmpeg.org' <ffmpeg-devel@ffmpeg.org>
> 主题: [PATCH] avcodec/v4l2_m2m: close the invalid file descriptor -1 in function v4l2_m2m_destroy_context
Maybe this title would be better?
avcodec/v4l2_m2m: Check if the file descriptor is valid before closing
Mention the trac ticket in the commit message please.
> Signed-off-by: wujian_nanjing <wujian2@huawei.com>
Remove the _?
> ---
> libavcodec/v4l2_m2m.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/libavcodec/v4l2_m2m.c b/libavcodec/v4l2_m2m.c index 51932ba..4427b48 100644
> --- a/libavcodec/v4l2_m2m.c
> +++ b/libavcodec/v4l2_m2m.c
> @@ -251,7 +251,9 @@ static void v4l2_m2m_destroy_context(void *opaque, uint8_t *context)
> ff_v4l2_context_release(&s->capture);
> sem_destroy(&s->refsync);
>
> - close(s->fd);
> + if (s->fd >= 0)
> + close(s->fd);
> +
The patch change looks fine, but it doesn't apply.
Thanks,
--
Andriy
_______________________________________________
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-06-25 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 3:04 Wujian(Chin)
2022-06-25 22:05 ` Andriy Gelman [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-15 11:14 [FFmpeg-devel] " Wujian(Chin)
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=20220625220550.7dj4zku4lte2atkf@jackie \
--to=andriy.gelman@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