Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: KaFai Wan <kafai.wan@linux.dev>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
	andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
	martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
	jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
	shuah@kernel.org, nathan@kernel.org, ndesaulniers@google.com,
	morbo@google.com, justinstitt@google.com, leon.hwang@linux.dev,
	donggeunyoo.kernel@gmail.com, menglong8.dong@gmail.com,
	yatsenko@meta.com, jiangfeng@kylinos.cn, vineet.gupta@linux.dev,
	puranjay@kernel.org, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	llvm@lists.linux.dev
Subject: Re: [PATCH bpf-next v3 0/4] selftests/bpf: Fix selftests fails with clang23
Date: Sun, 18 Oct 2026 22:50:06 +0000	[thread overview]
Message-ID: <179236380628.1845637.4163386381881195257.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261018005348.2195130-1-kafai.wan@linux.dev>

Hello:

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

On Sun, 18 Oct 2026 08:53:44 +0800 you wrote:
> Building with clang/LLVM 23 breaks several selftests. Patches #1 to #4 fix
> those failures.
> 
> Changes in v3:
>  - Remove the patch already applied.
> 
> Changes in v2:
>  - https://lore.kernel.org/bpf/20261014113043.640435-1-kafai.wan@linux.dev/
>  - Collect the selftest fixes from the two patches in v1
>    patches: #1, #5, #6 and #7.
>  - Add three new patches: #2, #3 and #4.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/4] bpf: Determine freplace staticness from BTF linkage
    https://git.kernel.org/bpf/bpf-next/c/0ceb2f21d3e0
  - [bpf-next,v3,2/4] selftests/bpf: Fix stack_arg precision backtracking log expectation
    https://git.kernel.org/bpf/bpf-next/c/8d637d4c62c1
  - [bpf-next,v3,3/4] selftests/bpf: Fix stack arg pruning test JOIN log expectation
    https://git.kernel.org/bpf/bpf-next/c/8342d47ad791
  - [bpf-next,v3,4/4] selftests/bpf: Use _exit() in uprobe_multi_test clone-ed child
    https://git.kernel.org/bpf/bpf-next/c/ce42271dc517

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



      parent reply	other threads:[~2026-10-18 22:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18  0:53 [PATCH bpf-next v3 0/4] selftests/bpf: Fix selftests fails with clang23 KaFai Wan
2026-10-18  0:53 ` [PATCH bpf-next v3 1/4] bpf: Determine freplace staticness from BTF linkage KaFai Wan
2026-10-18  0:53 ` [PATCH bpf-next v3 2/4] selftests/bpf: Fix stack_arg precision backtracking log expectation KaFai Wan
2026-10-18  0:53 ` [PATCH bpf-next v3 3/4] selftests/bpf: Fix stack arg pruning test JOIN " KaFai Wan
2026-10-18  0:53 ` [PATCH bpf-next v3 4/4] selftests/bpf: Use _exit() in uprobe_multi_test clone-ed child KaFai Wan
2026-10-18 22: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=179236380628.1845637.4163386381881195257.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=donggeunyoo.kernel@gmail.com \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=jiangfeng@kylinos.cn \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=justinstitt@google.com \
    --cc=kafai.wan@linux.dev \
    --cc=leon.hwang@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=menglong8.dong@gmail.com \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=puranjay@kernel.org \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=vineet.gupta@linux.dev \
    --cc=yatsenko@meta.com \
    --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