Received-SPF: pass (google.com: domain of linux-kernel+bounces-89402-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Sat, 2 Mar 2024 17:43:38 +0800
From: Philip Li <philip.li@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
CC: kernel test robot <lkp@intel.com>, <oe-kbuild-all@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, Arjan van de Ven <arjan@linux.intel.com>,
	<x86@kernel.org>
Subject: Re: arch/x86/include/asm/processor.h:698:16: sparse: sparse:
 incorrect type in initializer (different address spaces)
Message-ID: <ZeL0yknB10isSkQF@rli9-mobl>
References: <202403020457.RCJoQ3ts-lkp@intel.com>
 <87edctwr6y.ffs@tglx>
 <87a5nhwpus.ffs@tglx>
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <87a5nhwpus.ffs@tglx>
Precedence: bulk
MIME-Version: 1.0
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?us-ascii?Q?DKxBobJ4qxllUsJ37lspI+X9d9NKc/NF4Je+y7Ya50xUdqXXA+An6p2n4Y90?=
 =?us-ascii?Q?wnJDPNQHdggSdxXtOLA1p6+XXArGzhDxWA5bF71lzwu6LuZKh6XZSbwZyyzF?=
 =?us-ascii?Q?OvqrxCVhJdL2Bf7qw/6pL231AVCx6hM0vRPCu0AWJlBllVyWI5n8h6wu3e1l?=
 =?us-ascii?Q?CJzDnmSFvw7GRnIFO8HiR9fMG3zbKLyPU6Pm0Oxml246d3WJZYYO7EhFZE2o?=
 =?us-ascii?Q?PhDZe2l55MHyGj9mkjoD+OmPz23qiXZ/BcGCdBHrG63VEmJLhB+n3IwlfXCr?=
 =?us-ascii?Q?cQ6zIBrFl8BVpurgDPPXrzen8BlG1q4A7qPjUWlld5oCZs/vFeY5Ddusiw79?=
 =?us-ascii?Q?efcyt+4dhAHJHYB3YxWQMzb/j0BLQ5T9xaUTZ1tt5+dkcE5lx+YqOV/3+iLs?=
 =?us-ascii?Q?OWpst3zStJja1WUCdMn7jgLodDxngtJq8zB/z3km3nCZpu6E3xEBdGVDNugI?=
 =?us-ascii?Q?3bUuR89nWIhRfpy6MSs432bBqe0BBQPKAwPvFIrg35J/WKdZ9dhmj5XbWhvP?=
 =?us-ascii?Q?g37eg7wQ2oUxMj9q1fK5awC94iEvmBdZWbMQtmpJ89EcY20hdtC/9ufrhpWt?=
 =?us-ascii?Q?P3wwmdnRJC+St/CpADr8FAX/ZX5d0shLDJL7Vp5Ka4vF9OsrCST4DoiFfQni?=
 =?us-ascii?Q?SYrNORFnwQPD28E2cCOUrSm0mRpDS/s7A56gVTlGxfTGukT1xj4x+J/RnQN0?=
 =?us-ascii?Q?k6SfHwiXp4wtuAEnF7Pa9pgLJT9HFEKJdlYc0a9S25Orw7nNYEBgyF6VHeKH?=
 =?us-ascii?Q?9sGPe9pdXHDg7CzDuUvw95bTgeBMSiD6XZ4KhBVUQg6LUsREcqwqfZi0ON93?=
 =?us-ascii?Q?2W3unnyZ48/kuGEeFBrlzIBA9uAdD/PL4VMmYQIb/6s34o0t6nlg629kiI5C?=
 =?us-ascii?Q?SaEzQdDuEF+xcbECcPtGiLgpVXMNeQdbwFq4Id0qNP6B/g+RThrYy+PVvkqO?=
 =?us-ascii?Q?tK5KkYZMl8L82GeCr36KdeJdH/YKKDf/lJbJcnZ2bR9pIJsO5oETfCYjvbbx?=
 =?us-ascii?Q?xInFclqAFGBPN09aFapiZixHll75dQw4lQdZZ8iJcgPi8FWfMiTFScqF8y30?=
 =?us-ascii?Q?9yDT+zRVUBGf8Lvd+r8wKaCITyMYqKlBXx5vP3CaI5dZdAKoKnpvUD9wr3wf?=
 =?us-ascii?Q?dj+SedMiCzChhwLkGlz9LUMY/OXul4RqKreKpE0ThdcMPOA49LN88VKfOz1Y?=
 =?us-ascii?Q?6LvRGIfbgMfRhWYlPv2AP8iRdrsR+a9zbS1/SmWuoNisSZd9YxwZWyKtuLF5?=
 =?us-ascii?Q?XVSUsdCoY51bBuMMSrl+0S98c9F7WpROsBb/sPQEo0/HBz9KFW3m4tXvdNSf?=
 =?us-ascii?Q?n8iUqsQ0yQ/38oFoVB5fcykm4JMrL29yLYSx1t/uZt4rb+s36evIrn2YsfIs?=
 =?us-ascii?Q?+VPa5LSnUxjFb/gE7sxFgRtqHT+O1xgsZ0nYAixv/lfEXGL35cqld+P9x2KC?=
 =?us-ascii?Q?2vVzH7tLaCO7N+u8cM/eQDDO3M56kNh6g62ph9jQuZ0jhLMfLFA/+cCSElDb?=
 =?us-ascii?Q?lvh/Ekd9AucF3b7eoTuKjzFTOpi70BmzaBvycj+C7Kcxp+AqJbXljv7KN5Ua?=
 =?us-ascii?Q?SuCePTtSa1jMb/HzzYTii3ETLGN3kMTGWkGlxtIE?=
X-MS-Exchange-CrossTenant-Network-Message-Id: 94139713-19b3-4f93-3c08-08dc3a9d40f6
X-MS-Exchange-CrossTenant-AuthSource: SN6PR11MB3230.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 02 Mar 2024 09:43:45.7033
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 46c98d88-e344-4ed4-8496-4ed7712e255d
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: q83B+54Bp8JmQlr+EWkdKnP0OsF7x+XrVpd03F0l0Y19ohNFKwYIM0ToIT3EKggCWMX3HNrqQ9qcIeCJ3myhxw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN7PR11MB6994
X-OriginatorOrg: intel.com

On Fri, Mar 01, 2024 at 11:26:35PM +0100, Thomas Gleixner wrote:
> On Fri, Mar 01 2024 at 22:57, Thomas Gleixner wrote:
> 
> > On Sat, Mar 02 2024 at 04:12, kernel test robot wrote:
> >> FYI, the error/warning was bisected to this commit, please ignore it
> >> if it's irrelevant.
> >
> > I have no idea to which previous thread you are replying to because your
> > mail lacks any references.
> >
> >> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> >> head:   87adedeba51a822533649b143232418b9e26d08b
> >> commit: 6e29032340b60f7aa7475c8234b17273e4424007 x86/cpu: Move cpu_l[l2]c_id into topology info
> >> date:   5 months ago
> >> config: i386-randconfig-062-20240301 (https://download.01.org/0day-ci/archive/20240302/202403020457.RCJoQ3ts-lkp@intel.com/config)
> >> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> >> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240302/202403020457.RCJoQ3ts-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/202403020457.RCJoQ3ts-lkp@intel.com/
> >>
> >> sparse warnings: (new ones prefixed by >>)
> >>
> >> vim +698 arch/x86/include/asm/processor.h
> >>
> >>    695	
> >>    696	static inline u16 per_cpu_llc_id(unsigned int cpu)
> >>    697	{
> >>  > 698		return per_cpu(cpu_info.topo.llc_id, cpu);
> >>    699	}
> >>    700	
> >
> > This is bogus and I looked at another related bogosity today:
> >
> >   https://lore.kernel.org/all/202403010704.oGQZPu0P-lkp@intel.com
> >
> > which has similar complaints.

Really sorry about this Thomas, the empty sparse warning in the report is a regression
caused by latest bot change. The impacted sparse warning pattern is "incorrect type".

We will fix this ASAP, and reply to each bad report to paste the raw warnings. Sorry
for the trouble and time waste.

> >
> > So I went and downloaded the config and followed the reproduction
> > instructions except for one detail.
> >
> > The only difference is the sparse version:
> >
> >     1) I had the regular debian variant installed.
> >
> >        Version:  0.6.4 (Debian: 0.6.4-3)
> >
> >     2) I updated my sparse clone and rebuilt
> >
> >        Version:  v0.6.4-66-g0196afe16a50
> >
> > Neither one of them exposed the problem, but you are using:
> >
> >        sparse version: v0.6.4-66-g0196afe1-dirty
> >
> > which is obviously based on the latest upstream tree, but seems to have
> > some extra muck on top which I don't know what it is.

The extra change is mainly to make "incorrect type" kind warning more bisect
friendly to join multiple lines together to output, and the change effect is like

Turn raw output

        net/ipv4/tcp_cong.c:300:24: sparse: warning: incorrect type in initializer (different address spaces)
        net/ipv4/tcp_cong.c:300:24: sparse:    expected struct tcp_congestion_ops const [noderef] __rcu *__new
        net/ipv4/tcp_cong.c:300:24: sparse:    got struct tcp_congestion_ops *[assigned] ca

To below format

        net/ipv4/tcp_cong.c:300:24: sparse: sparse: incorrect type in initializer (different address spaces) @@     expected struct tcp_congestion_ops const [noderef] __rcu *__new @@     got struct
tcp_congestion_ops *[assigned] ca @@
        net/ipv4/tcp_cong.c:300:24: sparse:     expected struct tcp_congestion_ops const [noderef] __rcu *__new
        net/ipv4/tcp_cong.c:300:24: sparse:     got struct tcp_congestion_ops *[assigned] ca

Sorry for the confusion here for -dirty version.

> >
> > Does this reproduce with an unpatched upstream sparse for you?
> >
> > If so then I'm really curious why it does not reproduce here.
> 
> Sorry, my fault. I can reproduce now but it still does not make any
> sense. The code is correct...
> 
> Let me put something together which the sparse folks can digest.
> 
> Thanks,
> 
>         tglx
>