From: Leo Izen <leo.izen@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/hls: use av_strlcopy instead of strncpy
Date: Thu, 26 Oct 2023 07:08:47 -0400
Message-ID: <0b8dd24b-ee83-4832-a830-9b33bfad62c8@gmail.com> (raw)
In-Reply-To: <AS8P250MB0744A94329FC45843B406F958FDDA@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>
On 10/26/23 06:54, Andreas Rheinhardt wrote:
> Leo Izen:
>> Avoids a -Wstringop-truncation warning by using av_strlcopy instead of
>> strncpy.
>>
>> Signed-off-by: Leo Izen <leo.izen@gmail.com>
>> ---
>> libavformat/hls.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/libavformat/hls.c b/libavformat/hls.c
>> index f5f549b24d..076f92ecfb 100644
>> --- a/libavformat/hls.c
>> +++ b/libavformat/hls.c
>> @@ -543,7 +543,7 @@ static struct rendition *new_rendition(HLSContext *c, struct rendition_info *inf
>> int langlen = strlen(rend->language);
>> if (langlen < sizeof(rend->language) - 3) {
>> rend->language[langlen] = ',';
>> - strncpy(rend->language + langlen + 1, info->assoc_language,
>> + av_strlcpy(rend->language + langlen + 1, info->assoc_language,
>> sizeof(rend->language) - langlen - 2);
>> }
>> }
>
> Doesn't this just silence the warning instead of fixing the potential
> truncation?
>
> - Andreas
>
The semantics of strlcpy and strncpy are slightly different. strlcopy
*always* nul-terminates the destination string. strncpy zeroes the
buffer and then runs memcpy, so if it would overflow the buffer the
string ends up without a nul-terminator. The warning triggers because
the compiler thinks that case can occur.
- Leo Izen
_______________________________________________
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:[~2023-10-26 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 3:14 Leo Izen
2023-10-26 3:23 ` Steven Liu
2023-10-26 10:54 ` Andreas Rheinhardt
2023-10-26 11:08 ` Leo Izen [this message]
2023-10-26 11:32 ` Andreas Rheinhardt
2023-10-26 12:01 ` Leo Izen
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=0b8dd24b-ee83-4832-a830-9b33bfad62c8@gmail.com \
--to=leo.izen@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