BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	kernel-team@fb.com, emmanuel.deloget@eho.link
Subject: Re: [PATCH bpf-next] libbpf: add sane strncpy alternative and use it internally
Date: Tue, 14 Dec 2021 14:50:08 +0000	[thread overview]
Message-ID: <163949340894.7160.7599467135949464597.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211211004043.2374068-1-andrii@kernel.org>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Fri, 10 Dec 2021 16:40:43 -0800 you wrote:
> strncpy() has a notoriously error-prone semantics which makes GCC
> complain about it a lot (and quite often completely completely falsely
> at that). Instead of pleasing GCC all the time (-Wno-stringop-truncation
> is unfortunately only supported by GCC, so it's a bit too messy to just
> enable it in Makefile), add libbpf-internal libbpf_strlcpy() helper
> which follows what FreeBSD's strlcpy() does and what most people would
> expect from strncpy(): copies up to N-1 first bytes from source string
> into destination string and ensures zero-termination afterwards.
> 
> [...]

Here is the summary with links:
  - [bpf-next] libbpf: add sane strncpy alternative and use it internally
    https://git.kernel.org/bpf/bpf-next/c/9fc205b413b3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2021-12-14 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-11  0:40 [PATCH bpf-next] libbpf: add sane strncpy alternative and use it internally Andrii Nakryiko
2021-12-14 14:50 ` patchwork-bot+netdevbpf [this message]

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=163949340894.7160.7599467135949464597.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=emmanuel.deloget@eho.link \
    --cc=kernel-team@fb.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox