BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com
Subject: Re: [PATCH bpf-next 0/2] bpf: fix a couple of missed btf_type_tag handling in libbpf
Date: Tue, 16 Nov 2021 12:20:08 +0000	[thread overview]
Message-ID: <163706520863.24878.404260748653501732.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211115163932.3921753-1-yhs@fb.com>

Hello:

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

On Mon, 15 Nov 2021 08:39:32 -0800 you wrote:
> Commit 2dc1e488e5cd ("libbpf: Support BTF_KIND_TYPE_TAG") added
> BTF_KIND_TYPE_TAG support. But BTF_KIND_TYPE_TAG is not handled
> properly in libbpf btf_dedup_is_equiv() which will cause pahole dedup
> failure if the kernel has the following hack:
>   #define __user __attribute__((btf_type_tag("user")))
> 
> Patch 1 fixed the issue and Patch 2 added a test for it.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] libbpf: fix a couple of missed btf_type_tag handling in btf.c
    https://git.kernel.org/bpf/bpf-next/c/69a055d54615
  - [bpf-next,2/2] selftests/bpf: add a dedup selftest with equivalent structure types
    https://git.kernel.org/bpf/bpf-next/c/4746158305e9

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



      parent reply	other threads:[~2021-11-16 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 16:39 [PATCH bpf-next 0/2] bpf: fix a couple of missed btf_type_tag handling in libbpf Yonghong Song
2021-11-15 16:39 ` [PATCH bpf-next 1/2] libbpf: fix a couple of missed btf_type_tag handling in btf.c Yonghong Song
2021-11-15 16:39 ` [PATCH bpf-next 2/2] selftests/bpf: add a dedup selftest with equivalent structure types Yonghong Song
2021-11-16 12:27   ` Daniel Borkmann
2021-11-16 16:19     ` Yonghong Song
2021-11-16 12: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=163706520863.24878.404260748653501732.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 \
    --cc=yhs@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