BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org,
	kuba@kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix a btf_dump selftest failure
Date: Fri, 02 Aug 2024 19:30:31 +0000	[thread overview]
Message-ID: <172262703138.21946.6081334647905402907.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240802185434.1749056-1-yonghong.song@linux.dev>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Fri,  2 Aug 2024 11:54:34 -0700 you wrote:
> Jakub reported bpf selftest "btf_dump" failure after forwarding to
> v6.11-rc1 with netdev.
>   Error: #33 btf_dump
>   Error: #33/15 btf_dump/btf_dump: var_data
>     btf_dump_data:FAIL:find type id unexpected find type id: actual -2 < expected 0
> 
> The reason for the failure is due to
>   commit 94ede2a3e913 ("profiling: remove stale percpu flip buffer variables")
> where percpu static variable "cpu_profile_flip" is removed.
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Fix a btf_dump selftest failure
    https://git.kernel.org/bpf/bpf-next/c/3d650ab5e7d9

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



      reply	other threads:[~2024-08-02 19:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 18:54 [PATCH bpf-next] selftests/bpf: Fix a btf_dump selftest failure Yonghong Song
2024-08-02 19:30 ` 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=172262703138.21946.6081334647905402907.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=kuba@kernel.org \
    --cc=martin.lau@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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