From nobody Tue Apr 7 04:21:50 2026 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 718D41D9A54; Mon, 16 Mar 2026 10:06:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773655618; cv=none; b=sisy+i4/qLyCmDDRLg1GZoLOiwVWns59+ankC1Ms8wS8RhqXy09mBrZ5hFc8Av+OrwEikPiNsJvXx1OGSd7a/NBxIm390NGZx/Q2RwQRfL1Sk6SYuIFzNi5S58S8494zJFSUqJvDnqVQGhnKDj/53//2fFz1NKqkmCvOu4ogwm0= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773655618; c=relaxed/simple; bh=X/KDrnK2zADpCGQX7O2oTLqPN6C7uQkz394Z5wIa7kM=; h=Date:From:To:Subject:Cc:In-Reply-To:References:MIME-Version: Message-ID:Content-Type; b=SsVoA0V6OdMfo1MQpyMmmi5fniLX0A5VeSZf2EQSZnap+2Kf+2fAL1wjOODKNAqSDEmNAWGt0xvU2DlmCmn79p6dCOQYQFw95ur+q7jR6cDN5QNF+gKXl/8dr2WSO9qmOWLIhLcVAxEFtRworUdOR2q2fQKQxXOXO+CgQrie4mE= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=jWh21dmQ; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=6dkiiKyP; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="jWh21dmQ"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="6dkiiKyP" Date: Mon, 16 Mar 2026 10:06:54 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1773655616; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HK9jQcVy6G4op+f0QlVa2EFjPAnc7mFUd79I3rtH/cY=; b=jWh21dmQaM+Fr5Qbj03++R6Iwpsg3Oc425MiUH8gMHFpwhEwYT19RozGlXryObbMms1LHF cAlPw41YKkGI8ryDGYqkO1bCCsWZA9T9/DG+OzSGwFatGjSboQnGwQwglKyRn//+iGOKu3 uXm08pvOVkYPki/aNmImIAAfVP8MvQWKC6OvOcgnPr1hlRclw/OpMjrLgUT21PtHb6MQwq FTUqtEjrh0cJf5LmQdwMNECWYksMKW23Ksc09ZmjjH53oeDhomc+8lG6UWZOf/ENXPXbk/ bBJ9cTYRVYSTcX0g/Jx6IkGPiiuCG9qr/DyTqNhLPA609NU7obJ1XsYbLxP/wQ== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1773655616; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HK9jQcVy6G4op+f0QlVa2EFjPAnc7mFUd79I3rtH/cY=; b=6dkiiKyP0rXUtfCCBSl3xQuLJxtpB4YCM3H0GBpkp8UjAQbcM5DP7EiZFSGDC2YC4E5I60 zCckyHRmnrtHlGBw== From: "tip-bot2 for Bart Van Assche" Sender: tip-bot2@linutronix.de Reply-to: linux-kernel@vger.kernel.org To: linux-tip-commits@vger.kernel.org Subject: [tip: locking/urgent] include/linux/local_lock_internal.h: Make this header file again compatible with sparse Cc: kernel test robot , Bart Van Assche , "Peter Zijlstra (Intel)" , Marco Elver , x86@kernel.org, linux-kernel@vger.kernel.org In-Reply-To: <20260311231455.1961413-1-bvanassche@acm.org> References: <20260311231455.1961413-1-bvanassche@acm.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Message-ID: <177365561436.1647592.11094763824593026777.tip-bot2@tip-bot2> Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails Precedence: bulk Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable The following commit has been merged into the locking/urgent branch of tip: Commit-ID: 14de1552a4e3fece78bb20314887e70888c9d448 Gitweb: https://git.kernel.org/tip/14de1552a4e3fece78bb20314887e7088= 8c9d448 Author: Bart Van Assche AuthorDate: Wed, 11 Mar 2026 16:14:55 -07:00 Committer: Peter Zijlstra CommitterDate: Thu, 12 Mar 2026 11:29:11 +01:00 include/linux/local_lock_internal.h: Make this header file again compatible= with sparse There are two versions of the __this_cpu_local_lock() definitions in include/linux/local_lock_internal.h: one version that relies on the Clang overloading functionality and another version that does not. Select the latter version when using sparse. This patch fixes the following errors reported by sparse: include/linux/local_lock_internal.h:331:40: sparse: sparse: multiple def= initions for function '__this_cpu_local_lock' include/linux/local_lock_internal.h:325:37: sparse: the previous one is= here Closes: https://lore.kernel.org/oe-kbuild-all/202603062334.wgI5htP0-lkp@int= el.com/ Fixes: d3febf16dee2 ("locking/local_lock: Support Clang's context analysis") Reported-by: kernel test robot Signed-off-by: Bart Van Assche Signed-off-by: Peter Zijlstra (Intel) Reviewed-by: Marco Elver Link: https://patch.msgid.link/20260311231455.1961413-1-bvanassche@acm.org --- include/linux/local_lock_internal.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/local_lock_internal.h b/include/linux/local_lock= _internal.h index eff711b..234be7f 100644 --- a/include/linux/local_lock_internal.h +++ b/include/linux/local_lock_internal.h @@ -315,7 +315,7 @@ do { \ =20 #endif /* CONFIG_PREEMPT_RT */ =20 -#if defined(WARN_CONTEXT_ANALYSIS) +#if defined(WARN_CONTEXT_ANALYSIS) && !defined(__CHECKER__) /* * Because the compiler only knows about the base per-CPU variable, use th= is * helper function to make the compiler think we lock/unlock the @base var= iable,