BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: 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: Fix bpf_gotox with noipa global func
Date: Thu, 05 Nov 2026 01:30:12 +0000	[thread overview]
Message-ID: <179384221218.3342012.8649357736417717871.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261104214912.1543558-1-alexei.starovoitov@gmail.com>

Hello:

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

On Wed,  4 Nov 2026 21:49:12 +0000 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
> 
> use_nonstatic_global_other_sec() is an fentry prog, so it has to return 0.
> It returns the result of the global function __nonstatic_global(), which
> always returns 0.
> 
> Before llvm commit 28b4a2032f97 ("[BPF] Mark global functions noipa") the
> compiler replaced the result of the call with 0. Now it does not look into
> a global function. The verifier does not either:
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Fix bpf_gotox with noipa global func
    https://git.kernel.org/bpf/bpf-next/c/327c53dfd6b5

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



      reply	other threads:[~2026-11-05  1:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 21:49 [PATCH bpf-next] selftests/bpf: Fix bpf_gotox with noipa global func Alexei Starovoitov
2026-11-05  1: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=179384221218.3342012.8649357736417717871.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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 \
    /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