From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, lkp@intel.com, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org,
eddyz87@gmail.com, kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v1] bpf, x86: Fix objtool warning for timed may_goto
Date: Sat, 15 Mar 2025 23:00:29 +0000 [thread overview]
Message-ID: <174207962951.2670890.4290092846660019802.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250315013039.1625048-1-memxor@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 14 Mar 2025 18:30:39 -0700 you wrote:
> Kernel test robot reported "call without frame pointer save/setup"
> warning in objtool. This will make stack traces unreliable on
> CONFIG_UNWINDER_FRAME_POINTER=y, however it works on
> CONFIG_UNWINDER_ORC=y. Fix this by creating a stack frame for the
> function.
>
> Fixes: 2cb0a5215274 ("bpf, x86: Add x86 JIT support for timed may_goto")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202503071350.QOhsHVaW-lkp@intel.com/
> Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
>
> [...]
Here is the summary with links:
- [bpf-next,v1] bpf, x86: Fix objtool warning for timed may_goto
https://git.kernel.org/bpf/bpf-next/c/812f7702d83d
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:[~2025-03-15 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-15 1:30 [PATCH bpf-next v1] bpf, x86: Fix objtool warning for timed may_goto Kumar Kartikeya Dwivedi
2025-03-15 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=174207962951.2670890.4290092846660019802.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=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=lkp@intel.com \
--cc=martin.lau@kernel.org \
--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