mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yujie Liu <yujie.liu@intel.com>
To: kernel test robot <lkp@intel.com>
Cc: Brian Gerst <brgerst@gmail.com>, <oe-kbuild-all@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [tip:x86/boot 9/9] arch/x86/include/asm/desc.h:54:16: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Sat, 2 Mar 2024 21:02:25 +0800	[thread overview]
Message-ID: <ZeMjYfAUs74ey0oi@yujie-X299> (raw)
In-Reply-To: <202403021605.gg6Sr3yI-lkp@intel.com>

On Sat, Mar 02, 2024 at 04:19:58PM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/boot
> head:   721f791ce1cddfa5f2bf524ac14741bfa0f72697
> commit: 11e36b0f7c2150a6453872b79555767b43c846d0 [9/9] x86/boot/64: Load the final kernel GDT during early boot directly, remove startup_gdt[]
> config: x86_64-randconfig-121-20240301 (https://download.01.org/0day-ci/archive/20240302/202403021605.gg6Sr3yI-lkp@intel.com/config)
> compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240302/202403021605.gg6Sr3yI-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/202403021605.gg6Sr3yI-lkp@intel.com/
> 
> sparse warnings: (new ones prefixed by >>)

Sorry for the empty warning here. The actual sparse warning is:

arch/x86/include/asm/desc.h:54:16: sparse: sparse: incorrect type in initializer (different address spaces)
arch/x86/include/asm/desc.h:54:16: sparse:     expected void const [noderef] __percpu *__vpp_verify
arch/x86/include/asm/desc.h:54:16: sparse:     got struct gdt_page *

> 
> 
> vim +54 arch/x86/include/asm/desc.h
> 
> a939098afcfa5f include/asm-x86/desc.h      Glauber Costa  2008-05-28  50  
> 69218e47994da6 arch/x86/include/asm/desc.h Thomas Garnier 2017-03-14  51  /* Provide the original GDT */
> 69218e47994da6 arch/x86/include/asm/desc.h Thomas Garnier 2017-03-14  52  static inline struct desc_struct *get_cpu_gdt_rw(unsigned int cpu)
> a939098afcfa5f include/asm-x86/desc.h      Glauber Costa  2008-05-28  53  {
> a939098afcfa5f include/asm-x86/desc.h      Glauber Costa  2008-05-28 @54  	return per_cpu(gdt_page, cpu).gdt;
> a939098afcfa5f include/asm-x86/desc.h      Glauber Costa  2008-05-28  55  }
> a939098afcfa5f include/asm-x86/desc.h      Glauber Costa  2008-05-28  56  
> 
> :::::: The code at line 54 was first introduced by commit
> :::::: a939098afcfa5f81d3474782ec15c6d114e57763 x86: move x86_64 gdt closer to i386
> 
> :::::: TO: Glauber Costa <gcosta@redhat.com>
> :::::: CC: Ingo Molnar <mingo@elte.hu>
> 
> -- 
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
> 

      reply	other threads:[~2024-03-02 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02  8:19 kernel test robot
2024-03-02 13:02 ` Yujie Liu [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=ZeMjYfAUs74ey0oi@yujie-X299 \
    --to=yujie.liu@intel.com \
    --cc=brgerst@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mingo@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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®