All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Shung-Hsi Yu <shung-hsi.yu@suse.com>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Kumar Kartikeya Dwivedi <memxor@gmail.com>
Subject: Re: Mainline BPF selftests failure due to rcu_tasks_trace and do_filp_open changes
Date: Tue, 10 Feb 2026 16:08:22 -0800	[thread overview]
Message-ID: <33a19d40-e8f4-4eec-a82e-d0a1048a34a9@linux.dev> (raw)
In-Reply-To: <djwjf2vfb7gro3rfag666bojod6ytcectahnb5z6hx2hawimtj@sx47ghzjg4lw>

On 2/9/26 11:34 PM, Shung-Hsi Yu wrote:
> Testing with Linus' tree (4adc13ed7c28), BPF selftests in failing in the
> following cases across test_progs{,-no_alu32,-cpuv4}:
> 
> 1. map_kptr: failed to create kprobe 'rcu_tasks_trace_postgp+0x0'
> 
>    rcu_tasks_trace_postgp() no longer exists with commit c27cea4416a3
>    ("rcu: Re-implement RCU Tasks Trace in terms of SRCU-fast")[2]
> 
> 2. test_profiler: failed to create kretprobe 'do_filp_open+0x0'
> 
>    renamed to do_file_open() in commit 541003b576c3 ("rename
>    do_filp_open() to do_file_open()")[3]
> 

Hi Shung-Hsi,

I've just sent out a fix for test_profiler [1].

As for map_kptr, I disabled it temporarily on BPF CI.  I looked into
this a little, and the test relies on kprobing a static function,
which isn't very reliable.  Kumar has some ideas how to make the test
better, stay tuned.

[1] https://lore.kernel.org/bpf/20260210235855.215679-1-ihor.solodrai@linux.dev/

> Not familiar with when fix for these are usually done/sent. I suppose
> after 7.0-rc1?

AFAIU yes, the patches fixing this would go through -rc PRs.

> 
> 1: https://github.com/shunghsiyu/libbpf/actions/runs/21850240572/job/63055018509
> 2: https://lore.kernel.org/all/b206b083-f611-43b6-993f-78ddbe315813@paulmck-laptop/
> 3: https://lore.kernel.org/all/20260114043310.3885463-32-viro@zeniv.linux.org.uk/


  parent reply	other threads:[~2026-02-11  0:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10  7:34 Mainline BPF selftests failure due to rcu_tasks_trace and do_filp_open changes Shung-Hsi Yu
2026-02-10 21:00 ` Alexei Starovoitov
2026-02-12  6:15   ` Shung-Hsi Yu
2026-02-11  0:08 ` Ihor Solodrai [this message]
2026-02-12  6:18   ` Shung-Hsi Yu

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=33a19d40-e8f4-4eec-a82e-d0a1048a34a9@linux.dev \
    --to=ihor.solodrai@linux.dev \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=memxor@gmail.com \
    --cc=shung-hsi.yu@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.