From: Tejun Heo <tj@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: cgroups@vger.kernel.org, Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
loongarch@lists.linux.dev
Subject: Re: [tj-cgroup:for-next] BUILD REGRESSION a8d55ff5f3acf52e6380976fb5d0a9172032dcb0
Date: Tue, 28 May 2024 09:50:24 -1000 [thread overview]
Message-ID: <ZlY1gDDPi_mNrwJ1@slm.duckdns.org> (raw)
In-Reply-To: <202405271606.DYMCKs25-lkp@intel.com>
(cc'ing loongarch folks)
On Mon, May 27, 2024 at 04:14:10PM +0800, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-next
> branch HEAD: a8d55ff5f3acf52e6380976fb5d0a9172032dcb0 kernel/cgroup: cleanup cgroup_base_files when fail to add cgroup_psi_files
>
> Error/Warning reports:
>
> https://lore.kernel.org/oe-kbuild-all/202405270728.d1SabzhU-lkp@intel.com
>
> Error/Warning: (recently discovered and may have been fixed)
>
> kernel/cgroup/pids.o: warning: objtool: __jump_table+0x0: special: can't find orig instruction
>
> Error/Warning ids grouped by kconfigs:
>
> gcc_recent_errors
> `-- loongarch-defconfig
> `-- kernel-cgroup-pids.o:warning:objtool:__jump_table:special:can-t-find-orig-instruction
I don't know what to make of this build warning. I can't reproduce the
problem on x86 and the referenced commit doesn't have anything special. It
*looks* like it could be something specific to loongarch. Can you guys
please take a look?
Thanks.
--
tejun
next prev parent reply other threads:[~2024-05-28 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 8:14 [tj-cgroup:for-next] BUILD REGRESSION a8d55ff5f3acf52e6380976fb5d0a9172032dcb0 kernel test robot
2024-05-28 19:50 ` Tejun Heo [this message]
2024-05-29 0:28 ` Xi Ruoyao
2024-05-30 14:46 ` Huacai Chen
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=ZlY1gDDPi_mNrwJ1@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=lkp@intel.com \
--cc=loongarch@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