From: kernel test robot <lkp@intel.com>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Tony Luck <tony.luck@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@suse.de>
Subject: [intel-tdx:guest-upstream 5/32] arch/x86/coco/tdx/tdcall.o: warning: objtool: __tdx_module_call()+0x3a: missing int3 after ret
Date: Fri, 1 Apr 2022 15:08:46 +0800 [thread overview]
Message-ID: <202204011414.sHGf1lWN-lkp@intel.com> (raw)
Hi Kuppuswamy,
First bad commit (maybe != root cause):
tree: https://github.com/intel/tdx.git guest-upstream
head: 7d5c8afa0ebaf1731bb7ce8fe34a3248224fe0e9
commit: c03bec7b2dad416b31b8e5d5d656dfd84430ee09 [5/32] x86/tdx: Add __tdx_module_call() and __tdx_hypercall() helper functions
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220401/202204011414.sHGf1lWN-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-19) 11.2.0
reproduce (this is a W=1 build):
# https://github.com/intel/tdx/commit/c03bec7b2dad416b31b8e5d5d656dfd84430ee09
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx guest-upstream
git checkout c03bec7b2dad416b31b8e5d5d656dfd84430ee09
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash arch/x86/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/x86/coco/tdx/tdcall.o: warning: objtool: __tdx_module_call()+0x3a: missing int3 after ret
>> arch/x86/coco/tdx/tdcall.o: warning: objtool: __tdx_hypercall()+0x60: missing int3 after ret
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-01 7:10 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=202204011414.sHGf1lWN-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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 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.