From: patchwork-bot+netdevbpf@kernel.org
To: Jesus Sanchez-Palencia <jesussanp@google.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org, sdf@google.com,
rongtao@cestc.cn, daniel@iogearbox.net
Subject: Re: [PATCH] Revert "libbpf: Poison strlcpy()"
Date: Thu, 09 Mar 2023 01:40:18 +0000 [thread overview]
Message-ID: <167832601863.28104.18004021177531379064.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230309004836.2808610-1-jesussanp@google.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 8 Mar 2023 16:48:36 -0800 you wrote:
> This reverts commit 6d0c4b11e743("libbpf: Poison strlcpy()").
>
> It added the pragma poison directive to libbpf_internal.h to protect
> against accidental usage of strlcpy but ended up breaking the build for
> toolchains based on libcs which provide the strlcpy() declaration from
> string.h (e.g. uClibc-ng). The include order which causes the issue is:
>
> [...]
Here is the summary with links:
- Revert "libbpf: Poison strlcpy()"
https://git.kernel.org/bpf/bpf-next/c/3b83591e32dd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-03-09 1:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 0:48 [PATCH] Revert "libbpf: Poison strlcpy()" Jesus Sanchez-Palencia
2023-03-09 1:40 ` patchwork-bot+netdevbpf [this message]
2023-03-09 16:06 ` Jesus Sanchez-Palencia
2023-03-09 17:26 ` Andrii Nakryiko
2023-03-09 17:31 ` Jesus Sanchez-Palencia
2023-03-09 18:50 ` Daniel Borkmann
2023-03-09 19:03 ` Andrii Nakryiko
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=167832601863.28104.18004021177531379064.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jesussanp@google.com \
--cc=rongtao@cestc.cn \
--cc=sdf@google.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