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 3279536EAB8; Thu, 7 May 2026 10:09:45 +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=1778148593; cv=none; b=NCgM8/apbFrTdQOmTe8nktDqivh4rVrtN8WroBbIKjX5CLveiMCa+x8E1x1c9GUPpIbqQWDQJkig5CjfCBNlCl9xhgqgbhLSfUjNZAwrp6lHHt7bvjd687xZOYXYQWfeOB+sOjKxKrS5G0L5BQ0nbdaHi2Dsx1UZnrUh2yIP9cU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778148593; c=relaxed/simple; bh=3emQ/ccomwqisCwnCEFkzO8TAgXpYn3TuapgaXeKYiY=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=HbEdEjTsmXHDdTLMwT0b5MlelWZJ5cx8cZMVFahV8MZXJKQhn+RXrE+PgbqNr9p9eCA1UF8tHiX4xpDnGUqeRFSOhahGfVb5LwkHPMbnhqQGRS8Gu9f53qfL4wCm/iTDE0ViY/8+rnGrn99zJp4FERkGt/wWS5xiKhIjMnIk5TE= 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=LStILe0M; 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="LStILe0M" Received: from localhost (localhost [127.0.0.1]) by 013.lax.mailroute.net (Postfix) with ESMTP id 4gB7Js2s59zlfgQG; Thu, 7 May 2026 10:09:33 +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=1778148570; x=1780740571; bh=A2GCIRnbZ6EmuhFLdKfQezAA wWJlhXNQDmi93upPFlU=; b=LStILe0MDV3Kut67xXi6z2AxOV8fjWT5BPQ3Gshn 8NQxiUPr2a3Gw39Xjnc9YFiwKrDloaNjEoDRY0HSU2kgDzDHgEDRUtFKyV7BrXHU d7feVmJhguoQHd5Kt2SXLD0bsxlWm7STTEHClY2cKIoUgFSHFOPA4eZUpwH3Ixyf HGnO1u+7aB7rybHTLt+AD1wzW6fnvGREUxmUR+6LctCc2qwQoddd3E6ooWqcOs7H j6iSi8E3HCB7Of1stHytw9NH95HaJ57oU+gFNiFwusSm9oOQxkqzoYuFCzEkUo9j NQo5serppzDEFsHhFoyiVgkCsedMhi6a6RICs2J6KG6kOg== 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 UEJEX8bsTYQS; Thu, 7 May 2026 10:09:30 +0000 (UTC) Received: from [10.231.136.254] (46-253-189-47.dynamic.monzoon.net [46.253.189.47]) (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 4gB7Jm0YkpzlfwHS; Thu, 7 May 2026 10:09:27 +0000 (UTC) Message-ID: <0ffcd368-d4a1-4649-a75f-881b95fd4dbe@acm.org> Date: Thu, 7 May 2026 12:09:25 +0200 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/rtmutex: Annotate API and implementation To: Nathan Chancellor , Peter Zijlstra Cc: linux-tip-commits@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org References: <20260505022649.870788-1-bvanassche@acm.org> <177797853432.424702.11529123964407349507.tip-bot2@tip-bot2> <20260507084357.GA961911@ax162> Content-Language: en-US From: Bart Van Assche In-Reply-To: <20260507084357.GA961911@ax162> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 5/7/26 10:43 AM, Nathan Chancellor wrote: > On Tue, May 05, 2026 at 10:55:34AM -0000, tip-bot2 for Bart Van Assche wrote: >> The following commit has been merged into the locking/core branch of tip: >> >> Commit-ID: d30a456aa7ce1bab05d9b364eeacad0c9cb10cc2 >> Gitweb: https://git.kernel.org/tip/d30a456aa7ce1bab05d9b364eeacad0c9cb10cc2 >> Author: Bart Van Assche >> AuthorDate: Tue, 05 May 2026 04:26:44 +02:00 >> Committer: Peter Zijlstra >> CommitterDate: Tue, 05 May 2026 12:50:49 +02:00 >> >> locking/rtmutex: Annotate API and implementation >> >> Add lock context annotations to the rtmutex API and implementation and >> enable lock context analysis. >> >> Signed-off-by: Bart Van Assche >> Signed-off-by: Peter Zijlstra (Intel) >> Link: https://patch.msgid.link/20260505022649.870788-1-bvanassche@acm.org > > This breaks the build for me. > > $ make -skj"$(nproc)" ARCH=x86_64 LLVM=1 mrproper defconfig kernel/locking/rtmutex_api.o > kernel/locking/rtmutex_api.c:93:1: error: expecting rt_mutex 'lock' to be held at the end of function [-Werror,-Wthread-safety-analysis] > 93 | } > | ^ > kernel/locking/rtmutex_api.c:90:14: note: rt_mutex acquired here > 90 | void __sched rt_mutex_lock(struct rt_mutex *lock) > | ^ > 1 error generated. > > This is with LLVM 22.1.5, in case it matters. Hi Nathan, I think this is the same error as what has been reported by the kernel test robot (https://lore.kernel.org/all/202605060005.JYWpZXr2-lkp@intel.com/). I plan to post a new version with a fix for CONFIG_DEBUG_LOCK_ALLOC=n soon. Thanks, Bart.