From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (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 571623128CC; Mon, 22 Sep 2025 17:12:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.95.11.211 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758561153; cv=none; b=GWVPHH7VpwIc2YiAhlVwZOwXWas47UKl87CJYrbFeuaOXXGe0diwsruwprZ1wGimyz55hI/aZwXTisPIZ9E4sVJnMlclWYPJmJh7PYJZ3A4/R783SK3UKea7vBEKDyjEVGoXEQd0e/PyRWyutKdSpxl9BjfrPVps+jGddAp1Oh8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758561153; c=relaxed/simple; bh=8oIaUjkf1ZLoWcfViyJ+ASS1wRwmeYlliRHc+XNJKBU=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=BXa6gg4eHn8PBiaT9Far/1n6x9CEVirjcmqbOon8aQ5OWUiW6ySDlG2/dQh8rY3EbvQIF+sRfWM5pqWqfXJoEpYnVlxTziQPg+KI5aqWAvpm9UAaMAqAskJ3EJL1Msdz+slXwgBW3kovj+xGiiEA5c/aQYO9avgcUfQj2WKPxPM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lst.de; spf=pass smtp.mailfrom=lst.de; arc=none smtp.client-ip=213.95.11.211 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lst.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lst.de Received: by verein.lst.de (Postfix, from userid 2407) id 6B6BB227AAF; Mon, 22 Sep 2025 19:12:27 +0200 (CEST) Date: Mon, 22 Sep 2025 19:12:27 +0200 From: Christoph Hellwig To: Bart Van Assche Cc: Christoph Hellwig , Nathan Chancellor , Marco Elver , Peter Zijlstra , Boqun Feng , Ingo Molnar , Will Deacon , "David S. Miller" , Luc Van Oostenryck , "Paul E. McKenney" , Alexander Potapenko , Arnd Bergmann , Bill Wendling , Dmitry Vyukov , Eric Dumazet , Frederic Weisbecker , Greg Kroah-Hartman , Herbert Xu , Ian Rogers , Jann Horn , Joel Fernandes , Jonathan Corbet , Josh Triplett , Justin Stitt , Kees Cook , Kentaro Takeda , Lukas Bulwahn , Mark Rutland , Mathieu Desnoyers , Miguel Ojeda , Neeraj Upadhyay , Nick Desaulniers , Steven Rostedt , Tetsuo Handa , Thomas Gleixner , Thomas Graf , Uladzislau Rezki , Waiman Long , kasan-dev@googlegroups.com, linux-crypto@vger.kernel.org, linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-security-module@vger.kernel.org, linux-sparse@vger.kernel.org, llvm@lists.linux.dev, rcu@vger.kernel.org Subject: Re: [PATCH v3 00/35] Compiler-Based Capability- and Locking-Analysis Message-ID: <20250922171227.GB12668@lst.de> References: <20250918140451.1289454-1-elver@google.com> <20250918141511.GA30263@lst.de> <20250918174555.GA3366400@ax162> <20250919140803.GA23745@lst.de> Precedence: bulk X-Mailing-List: linux-kbuild@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) On Fri, Sep 19, 2025 at 10:20:37AM -0700, Bart Van Assche wrote: > locking annotations to kernel code. I ended up annotating multiple XFS > functions with NO_THREAD_SAFETY_ANALYSIS. Maybe the locking patterns in > XFS are too complex for compile-time analysis? If our locking patterns are too complex for analysis, either the code or the analysis has problems that need addressing. Potentially both.