BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
	eddyz87@gmail.com, memxor@gmail.com, tglx@kernel.org,
	bpf@vger.kernel.org
Subject: Re: [PATCH bpf v2] selftests/bpf: Use both hrtimer enqueue helpers in vmlinux test
Date: Mon, 11 May 2026 23:00:17 +0000	[thread overview]
Message-ID: <177854041705.2496500.7441021912913320811.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260509005730.250956-1-ihor.solodrai@linux.dev>

Hello:

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

On Fri,  8 May 2026 17:57:30 -0700 you wrote:
> The vmlinux selftest triggers nanosleep and checks that both kprobe
> and fentry programs observe the hrtimer enqueue path.
> 
> After the hrtimer_start_expires_user() conversion [1], nanosleep
> reaches hrtimer_start_range_ns_user() instead of
> hrtimer_start_range_ns(). Hard-coding either symbol makes the test
> fail either on bpf tree or on linux-next [2].
> 
> [...]

Here is the summary with links:
  - [bpf,v2] selftests/bpf: Use both hrtimer enqueue helpers in vmlinux test
    https://git.kernel.org/bpf/bpf-next/c/25bb05dd06cc

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-05-11 23:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-09  0:57 [PATCH bpf v2] selftests/bpf: Use both hrtimer enqueue helpers in vmlinux test Ihor Solodrai
2026-05-11  7:04 ` Jiri Olsa
2026-05-11 23:00 ` 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=177854041705.2496500.7441021912913320811.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=eddyz87@gmail.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=memxor@gmail.com \
    --cc=tglx@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