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
Subject: Re: [PATCH bpf-next 1/2] libbpf: use strlcpy() in path resolution fallback logic
Date: Fri, 08 Apr 2022 16:20:14 +0000	[thread overview]
Message-ID: <164943481429.8672.18385222522361817254.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220407230446.3980075-1-andrii@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu, 7 Apr 2022 16:04:45 -0700 you wrote:
> Coverity static analyzer complains that strcpy() can cause buffer
> overflow. Use libbpf_strlcpy() instead to be 100% sure this doesn't
> happen.
> 
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
> ---
>  tools/lib/bpf/usdt.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Here is the summary with links:
  - [bpf-next,1/2] libbpf: use strlcpy() in path resolution fallback logic
    https://git.kernel.org/bpf/bpf-next/c/3c0dfe6e4c43
  - [bpf-next,2/2] libbpf: allow WEAK and GLOBAL bindings during BTF fixup
    https://git.kernel.org/bpf/bpf-next/c/3a06ec0a996d

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



      parent reply	other threads:[~2022-04-08 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 23:04 [PATCH bpf-next 1/2] libbpf: use strlcpy() in path resolution fallback logic Andrii Nakryiko
2022-04-07 23:04 ` [PATCH bpf-next 2/2] libbpf: allow WEAK and GLOBAL bindings during BTF fixup Andrii Nakryiko
2022-04-08 16:20 ` 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=164943481429.8672.18385222522361817254.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=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