From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 013.lax.mailroute.net (013.lax.mailroute.net [199.89.1.16]) (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 D360A391850; Thu, 12 Mar 2026 16:36:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=199.89.1.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773333380; cv=none; b=GvknNP25X7yBxP7FmJiPGNte3WQ7x7aPOpWUgzUAtyGUzz74vk9nCPtaBl2UgQ/oSc8Ftgz3+0qu5HfpSCoCHm/XPwBirMlBy5vTEECO6FAFjFfimPW+Vyr3q7oJLxbO1xYo29nUwLLet+45UbQzu4G/nBG8zBZ1PssevxXaBGY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773333380; c=relaxed/simple; bh=ViHu4Mtq0pLqsq4ayrq56XoB44Hpsj2gQwd0cx9vnPY=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=Z/mrkHIxZ5QbJ8e4TVAMNbM2QioNqq7g/9Q3H+krLdLNPtqpxjVpFRVaIzJdSXuRPUnHaKySBiU0296Rjh0mlQEBOTNcRaVSocBl1l8hWUZUNKmdul8nI8HgKkAvLOh0iEEk3Po/pZZvqtnCaBdA/9seUCkZhWqwJwBTUivJ8a0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=acm.org; spf=pass smtp.mailfrom=acm.org; dkim=pass (2048-bit key) header.d=acm.org header.i=@acm.org header.b=dJ/xdvuJ; arc=none smtp.client-ip=199.89.1.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=acm.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=acm.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=acm.org header.i=@acm.org header.b="dJ/xdvuJ" Received: from localhost (localhost [127.0.0.1]) by 013.lax.mailroute.net (Postfix) with ESMTP id 4fWtXy2rX1zlfl8L; Thu, 12 Mar 2026 16:36:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=acm.org; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:content-language:references:subject:subject :user-agent:mime-version:date:date:message-id:received:received; s=mr01; t=1773333375; x=1775925376; bh=PMWTPjCdxCxjKJGI/2vQODro R5NKONABV7FccsOFLd0=; b=dJ/xdvuJtFNFX473PSrB1o35k66YNTe8piLToCgo hEB3PdhYCUjBRNTJD8betrrUwqaccupKKrD5qHfEjDzuSF8X0tahBfFud5Ep3acl NAAXVxQQIXRepk/hIAoWE0EimdviX/NaYtVgEjdkgzJvgkCIbd/Bie/0tsRHFrDI PcJEq0dRAEVeeeYemaPgpq/aVHIqjZmPWeXyk41XuWJtUm5TuDuhPfBS7AeESGF6 ilXdOBax7/er1RM9KDQbYEypxGOgyYVRR8Mr8phePxwzh6509u9tksEqvQGHvSqB yfPFzxizFDlaKh3ZreI4aBhN1BUxVScG25PfGttY9YPJYg== X-Virus-Scanned: by MailRoute Received: from 013.lax.mailroute.net ([127.0.0.1]) by localhost (013.lax [127.0.0.1]) (mroute_mailscanner, port 10029) with LMTP id 1UcZyzkV8phJ; Thu, 12 Mar 2026 16:36:15 +0000 (UTC) Received: from [100.119.48.131] (unknown [104.135.180.219]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: bvanassche@acm.org) by 013.lax.mailroute.net (Postfix) with ESMTPSA id 4fWtXs74ybzlfl7l; Thu, 12 Mar 2026 16:36:13 +0000 (UTC) Message-ID: <66c850f8-c4bd-4387-881e-01d3e1f402c4@acm.org> Date: Thu, 12 Mar 2026 09:36:09 -0700 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [tip: locking/core] locking: Fix rwlock and spinlock lock context annotations To: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org Cc: "Peter Zijlstra (Intel)" , Marco Elver , x86@kernel.org References: <20260225183244.4035378-2-bvanassche@acm.org> <177227618921.1647592.10577654819420686202.tip-bot2@tip-bot2> Content-Language: en-US From: Bart Van Assche In-Reply-To: <177227618921.1647592.10577654819420686202.tip-bot2@tip-bot2> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 2/28/26 2:56 AM, tip-bot2 for Bart Van Assche wrote: > The following commit has been merged into the locking/core branch of tip: > > Commit-ID: 38e18d825f7281fdc16d3241df5115ce6eaeaf79 > Gitweb: https://git.kernel.org/tip/38e18d825f7281fdc16d3241df5115ce6eaeaf79 > Author: Bart Van Assche > AuthorDate: Wed, 25 Feb 2026 10:32:41 -08:00 > Committer: Peter Zijlstra > CommitterDate: Fri, 27 Feb 2026 16:40:19 +01:00 > > locking: Fix rwlock and spinlock lock context annotations Hi Peter, Thank you for having queued this patch. Since some of my other patches depend on this patch, will this patch be sent to Linus during the current rc cycle? I'm asking this because I can't find this patch in Linus' master branch: $ git fetch origin $ git log --reverse --format=oneline v6.19..origin/master include/linux/rwlock_api_smp.h f16a802d402d735a55731f8c94952b3bbb5ddfe8 locking/rwlock, spinlock: Support Clang's context analysis e4588c25c9d122b5847b88e18b184404b6959160 compiler-context-analysis: Remove __cond_lock() function-like helper 7a562d5d2396c9c78fbbced7ae81bcfcfa0fde3f (tag: locking-core-2026-02-08) locking/rwlock: Fix write_trylock_irqsave() with CONFIG_INLINE_WRITE_TRYLOCK Thanks, Bart.