From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org,
sdf@google.com, haoluo@google.com
Subject: Re: [PATCHv2 bpf-next] selftests/bpf: Mark uprobe trigger functions with nocf_check attribute
Date: Fri, 22 Mar 2024 17:10:29 +0000 [thread overview]
Message-ID: <171112742973.3285.4148849344808411338.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240322134936.1075395-1-jolsa@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 22 Mar 2024 14:49:36 +0100 you wrote:
> Some distros seem to enable the -fcf-protection=branch by default,
> which breaks our setup on first instruction of uprobe trigger
> functions and place there endbr64 instruction.
>
> Marking them with nocf_check attribute to skip that.
>
> Ignoring unknown attribute warning in gcc for bench objects, because
> nocf_check can be used only when -fcf-protection=branch is enabled,
> otherwise we get a warning and break compilation.
>
> [...]
Here is the summary with links:
- [PATCHv2,bpf-next] selftests/bpf: Mark uprobe trigger functions with nocf_check attribute
https://git.kernel.org/bpf/bpf-next/c/af8d27bf15c8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-22 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 13:49 [PATCHv2 bpf-next] selftests/bpf: Mark uprobe trigger functions with nocf_check attribute Jiri Olsa
2024-03-22 17:10 ` 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=171112742973.3285.4148849344808411338.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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