From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "kernel test robot" <lkp@intel.com>,
"Alexei Starovoitov" <ast@kernel.org>
Cc: <oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: vmlinux.o: error: objtool: do_jit+0x4f77: relocation to !ENDBR: .text+0x24c3b5
Date: Mon, 26 Oct 2026 01:52:11 +0000 [thread overview]
Message-ID: <DMEE75PI8G2P.1AKZRLWQKYJ4C@gmail.com> (raw)
In-Reply-To: <202610252131.3Wl3JYJ5-lkp@intel.com>
On Sun Oct 25, 2026 at 8:17 PM UTC, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 21a7f44fd0765fcc5194130b28767786eba1d1e7
> commit: cff94a3d78d8cc12ceaf60aa9272aac422b1dc39 bpf, x86: Support unwind_goto and unwind_exit
> date: 5 days ago
> config: x86_64-randconfig-r2107-20261025 (https://download.01.org/0day-ci/archive/20261025/202610252131.3Wl3JYJ5-lkp@intel.com/config)
> compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261025/202610252131.3Wl3JYJ5-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Fixes: cff94a3d78d8 ("bpf, x86: Support unwind_goto and unwind_exit")
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202610252131.3Wl3JYJ5-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>>> vmlinux.o: error: objtool: do_jit+0x4f77: relocation to !ENDBR: .text+0x24c3b5
already fixed in bpf tree.
prev parent reply other threads:[~2026-10-26 1:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 20:17 kernel test robot
2026-10-26 1:52 ` Alexei Starovoitov [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=DMEE75PI8G2P.1AKZRLWQKYJ4C@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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
all inboxes | Powered by JetHome®