From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev
Subject: [peterz-queue:objtool/core 3/12] arch/x86/kvm/kvm.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
Date: Tue, 26 Nov 2024 05:00:45 +0800 [thread overview]
Message-ID: <202411260421.4JBdFPW5-lkp@intel.com> (raw)
TO: Peter Zijlstra <peterz@infradead.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git objtool/core
head: a5091c456d5d4e22f5729d7600080b18a37f10a2
commit: f4b16a1d266666624331222f640e9de652bc1dd4 [3/12] objtool: Convert ANNOTATE_NOENDBR to ANNOTATE
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20241126/202411260421.4JBdFPW5-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241126/202411260421.4JBdFPW5-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
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202411260421.4JBdFPW5-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/x86/kvm/kvm.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
>> drivers/nvme/host/nvme-core.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
>> drivers/nvme/target/nvmet.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
>> net/wireless/cfg80211.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
>> net/mac80211/mac80211.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
>> drivers/ufs/core/ufshcd-core.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
>> drivers/scsi/pm8001/pm80xx.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
>> drivers/scsi/qla2xxx/qla2xxx.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
>> fs/ext2/ext2.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
>> fs/nfsd/nfsd.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
--
>> fs/fuse/fuse.o: warning: objtool: .discard.annotate_insn: dodgy linker, sh_entsize != 8
..
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-11-25 21:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202411260421.4JBdFPW5-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.