mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Huang, Kai" <kai.huang@intel.com>
To: "mingo@kernel.org" <mingo@kernel.org>
Cc: "Hansen, Dave" <dave.hansen@intel.com>,
	"bp@alien8.de" <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"kirill.shutemov@linux.intel.com"
	<kirill.shutemov@linux.intel.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"jpoimboe@kernel.org" <jpoimboe@kernel.org>,
	"nik.borisov@suse.com" <nik.borisov@suse.com>,
	"sathyanarayanan.kuppuswamy@linux.intel.com" 
	<sathyanarayanan.kuppuswamy@linux.intel.com>
Subject: Re: [PATCH] x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed()
Date: Mon, 18 Sep 2023 03:57:01 +0000	[thread overview]
Message-ID: <c14474b7e646fc861e5aeae704705645ce6fa24e.camel@intel.com> (raw)
In-Reply-To: <ZQRNiTVQu23wFC/d@gmail.com>

On Fri, 2023-09-15 at 14:26 +0200, Ingo Molnar wrote:
> * Kai Huang <kai.huang@intel.com> wrote:
> 
> > LKP reported below build warning:
> > 
> >   vmlinux.o: warning: objtool: __tdx_hypercall+0x128: __tdx_hypercall_failed() is missing a __noreturn annotation
> > 
> > Turns out the __noreturn must be annotated to the function declaration
> > but not the function body.
> > 
> > Quoted from PeterZ:
> > 
> > ---
> > FWIW, the reason being that...
> > 
> > The point of noreturn is that the caller should know to stop generating
> > code. For that the declaration needs the attribute, because call sites
> > typically do not have access to the function definition in C.
> > ---
> > 
> > Fix by moving __noreturn annotation from the __tdx_hypercall_failed()
> > body to its declaration, which is in <asm/shared/tdx.h>.
> > 
> > Note <asm/shared/tdx.h> is also included by TDX related assembly files.
> > Include <linux/compiler_attributes.h> only in case of !__ASSEMBLY__
> > otherwise compiling assembly file would trigger build error.
> > 
> > Also, following the objtool documentation, add __tdx_hypercall_failed()
> > to "tools/objtool/noreturns.h".
> > 
> > Fixes: c641cfb5c157 ("x86/tdx: Make TDX_HYPERCALL asm similar to TDX_MODULE_CALL")
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202309140828.9RdmlH2Z-lkp@intel.com/
> > Signed-off-by: Kai Huang <kai.huang@intel.com>
> > ---
> >  arch/x86/coco/tdx/tdx.c           | 2 +-
> >  arch/x86/include/asm/shared/tdx.h | 4 +++-
> >  tools/objtool/noreturns.h         | 1 +
> >  3 files changed, 5 insertions(+), 2 deletions(-)
> > 
> > diff --git a/arch/x86/coco/tdx/tdx.c b/arch/x86/coco/tdx/tdx.c
> > index 3e6dbd2199cf..4710d8dd700b 100644
> > --- a/arch/x86/coco/tdx/tdx.c
> > +++ b/arch/x86/coco/tdx/tdx.c
> > @@ -38,7 +38,7 @@
> >  #define TDREPORT_SUBTYPE_0	0
> >  
> >  /* Called from __tdx_hypercall() for unrecoverable failure */
> > -noinstr void __noreturn __tdx_hypercall_failed(void)
> > +noinstr void __tdx_hypercall_failed(void)
> >  {
> 
> It's not a bad idea to document the __noreturn nature at the definition 
> site either, so I don't think we should remove it.
> 
> 

Thanks for feedback! I'll fix and send out v2.

Since it's a simple fix, I'll send out v2 shortly.

      reply	other threads:[~2023-09-18  4:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15 12:12 Kai Huang
2023-09-15 12:26 ` Ingo Molnar
2023-09-18  3:57   ` Huang, Kai [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=c14474b7e646fc861e5aeae704705645ce6fa24e.camel@intel.com \
    --to=kai.huang@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@kernel.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=nik.borisov@suse.com \
    --cc=peterz@infradead.org \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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®