From: kernel test robot <lkp@intel.com>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [kkdwivedi:timed-may-goto 1/1] vmlinux.o: warning: objtool: arch_bpf_timed_may_goto+0x24: 'naked' return found in MITIGATION_RETHUNK build
Date: Mon, 3 Mar 2025 00:24:59 +0800 [thread overview]
Message-ID: <202503030030.6pMxpW2c-lkp@intel.com> (raw)
tree: https://github.com/kkdwivedi/linux timed-may-goto
head: 45ff7356c9ab73e7534fd1a2aca784c8bab7eedb
commit: 45ff7356c9ab73e7534fd1a2aca784c8bab7eedb [1/1] bpf: Implement timed may_goto support
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20250303/202503030030.6pMxpW2c-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250303/202503030030.6pMxpW2c-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/202503030030.6pMxpW2c-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> vmlinux.o: warning: objtool: arch_bpf_timed_may_goto+0x24: 'naked' return found in MITIGATION_RETHUNK build
vmlinux.o: warning: objtool: nvmet_ctrl_state_show() falls through to next function __cfi_nvmet_ctrl_host_traddr_open()
vmlinux.o: warning: objtool: amd_set_spi_freq() falls through to next function amd_spi_busy_wait()
vmlinux.o: warning: objtool: tw28_set_ctrl_val() falls through to next function __cfi_tw28_get_ctrl_val()
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-02 16:25 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=202503030030.6pMxpW2c-lkp@intel.com \
--to=lkp@intel.com \
--cc=memxor@gmail.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 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.