BPF List
 help / color / mirror / Atom feed
From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: patchwork-bot+netdevbpf@kernel.org,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	eddyz87@gmail.com, memxor@gmail.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Don't include <linux/ptrace.h> in BPF progs
Date: Mon, 9 Nov 2026 16:17:57 -0700	[thread overview]
Message-ID: <547975dd-9e47-40e8-b043-b93e2026d288@linux.dev> (raw)
In-Reply-To: <179416380493.1666345.8032685838291433805.git-patchwork-notify@kernel.org>

On 11/8/26 11:50 AM, patchwork-bot+netdevbpf@kernel.org wrote:
> Hello:
> 
> This patch was applied to bpf/bpf-next.git (master)
> by Alexei Starovoitov <ast@kernel.org>:

Alexei,

I added this patch to BPF CI diffs today, but it doesn't apply to bpf,
and so aarch64 selftests build on bpf-targeting branches and on
linux-next remains broken:
* https://github.com/kernel-patches/bpf/actions/runs/42712433047/job/129485446405
* https://github.com/kernel-patches/bpf/actions/runs/42679811664/job/129371245681

I think this should've gone through the bpf tree. Fixing bpf now
separately will likely cause conflicts later.

> 
> On Sun,  8 Nov 2026 16:37:10 +0000 you wrote:
>> From: Alexei Starovoitov <ast@kernel.org>
>>
>> BPF CI cannot build the selftests on aarch64 since its image has new
>> kernel headers:
>>
>>   CLNG-BPF [test_progs] freplace_attach_probe.bpf.o
>>   In file included from progs/freplace_attach_probe.c:4:
>>   In file included from /usr/include/linux/ptrace.h:188:
>>   /usr/include/aarch64-linux-gnu/asm/ptrace.h:96:2: error: unknown type name '__u128'
>>      96 |         __u128          vregs[32];
>>
>> [...]
> 
> Here is the summary with links:
>   - [bpf-next] selftests/bpf: Don't include <linux/ptrace.h> in BPF progs
>     https://git.kernel.org/bpf/bpf-next/c/a0a0c785cbca
> 
> You are awesome, thank you!


      reply	other threads:[~2026-11-09 23:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-08 16:37 [PATCH bpf-next] selftests/bpf: Don't include <linux/ptrace.h> in BPF progs Alexei Starovoitov
2026-11-08 18:50 ` patchwork-bot+netdevbpf
2026-11-09 23:17   ` Ihor Solodrai [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=547975dd-9e47-40e8-b043-b93e2026d288@linux.dev \
    --to=ihor.solodrai@linux.dev \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=memxor@gmail.com \
    --cc=patchwork-bot+netdevbpf@kernel.org \
    /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