Changes in Makefile.context-analysis

c17ee635fd3a482b2ad2bf5e269755c2eae5f25e - Merge drm/drm-fixes into drm-misc-fixes

Mon, 23 Feb 2026 10:09:45 +0100

Merge drm/drm-fixes into drm-misc-fixes7.0-rc1 was just released, let's merge it to kick the new release cycle.Signed-off-by: Maxime Ripard List of files: /linux/scripts/Makefile.context-analysis

0923fd0419a1a2c8846e15deacac11b619e996d9 - Merge tag 'locking-core-2026-02-08' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

Tue, 10 Feb 2026 21:28:44 +0100

Merge tag 'locking-core-2026-02-08' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tipPull locking updates from Ingo Molnar: "Lock debugging: - Implement compiler-driven static analysis locking context checking, using the upcoming Clang 22 compiler's context analysis features (Marco Elver) We removed Sparse context analysis support, because prior to removal even a defconfig kernel produced 1,700+ context tracking Sparse warnings, the overwhelming majority of which are false positives. On an allmodconfig kernel the number of false positive context tracking Sparse warnings grows to over 5,200... On the plus side of the balance actual locking bugs found by Sparse context analysis is also rather ... sparse: I found only 3 such commits in the last 3 years. So the rate of false positives and the maintenance overhead is rather high and there appears to be no active policy in place to achieve a zero-warnings baseline to move the annotations & fixers to developers who introduce new code. Clang context analysis is more complete and more aggressive in trying to find bugs, at least in principle. Plus it has a different model to enabling it: it's enabled subsystem by subsystem, which results in zero warnings on all relevant kernel builds (as far as our testing managed to cover it). Which allowed us to enable it by default, similar to other compiler warnings, with the expectation that there are no warnings going forward. This enforces a zero-warnings baseline on clang-22+ builds (Which are still limited in distribution, admittedly) Hopefully the Clang approach can lead to a more maintainable zero-warnings status quo and policy, with more and more subsystems and drivers enabling the feature. Context tracking can be enabled for all kernel code via WARN_CONTEXT_ANALYSIS_ALL=y (default disabled), but this will generate a lot of false positives. ( Having said that, Sparse support could still be added back, if anyone is interested - the removal patch is still relatively straightforward to revert at this stage. ) Rust integration updates: (Alice Ryhl, Fujita Tomonori, Boqun Feng) - Add support for Atomic and replace most Rust native AtomicBool usages with Atomic - Clean up LockClassKey and improve its documentation - Add missing Send and Sync trait implementation for SetOnce - Make ARef Unpin as it is supposed to be - Add __rust_helper to a few Rust helpers as a preparation for helper LTO - Inline various lock related functions to avoid additional function calls WW mutexes: - Extend ww_mutex tests and other test-ww_mutex updates (John Stultz) Misc fixes and cleanups: - rcu: Mark lockdep_assert_rcu_helper() __always_inline (Arnd Bergmann) - locking/local_lock: Include more missing headers (Peter Zijlstra) - seqlock: fix scoped_seqlock_read kernel-doc (Randy Dunlap) - rust: sync: Replace `kernel::c_str!` with C-Strings (Tamir Duberstein)"* tag 'locking-core-2026-02-08' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (90 commits) locking/rwlock: Fix write_trylock_irqsave() with CONFIG_INLINE_WRITE_TRYLOCK rcu: Mark lockdep_assert_rcu_helper() __always_inline compiler-context-analysis: Remove __assume_ctx_lock from initializers tomoyo: Use scoped init guard crypto: Use scoped init guard kcov: Use scoped init guard compiler-context-analysis: Introduce scoped init guards cleanup: Make __DEFINE_LOCK_GUARD handle commas in initializers seqlock: fix scoped_seqlock_read kernel-doc tools: Update context analysis macros in compiler_types.h rust: sync: Replace `kernel::c_str!` with C-Strings rust: sync: Inline various lock related methods rust: helpers: Move #define __rust_helper out of atomic.c rust: wait: Add __rust_helper to helpers rust: time: Add __rust_helper to helpers rust: task: Add __rust_helper to helpers rust: sync: Add __rust_helper to helpers rust: refcount: Add __rust_helper to helpers rust: rcu: Add __rust_helper to helpers rust: processor: Add __rust_helper to helpers ... List of files: /linux/scripts/Makefile.context-analysis

c237f1ceeef56fa101c2b599a00307b3d690801a - compiler-context-analysis: Introduce header suppressions

Fri, 19 Dec 2025 16:40:14 +0100

compiler-context-analysis: Introduce header suppressionsWhile we can opt in individual subsystems which add the requiredannotations, such subsystems inevitably include headers from othersubsystems which may not yet have the right annotations, which thenresult in false positive warnings.Making compatible by adding annotations across all common headerscurrently requires an excessive number of __no_context_analysisannotations, or carefully analyzing non-trivial cases to add the correctannotations. While this is desirable long-term, providing an incrementalpath causes less churn and headaches for maintainers not yet interestedin dealing with such warnings.Rather than clutter headers unnecessary and mandate all subsystemmaintainers to keep their headers working with context analysis,suppress all -Wthread-safety warnings in headers. Explicitly opt inheaders with context-enabled primitives.With this in place, we can start enabling the analysis on more complexsubsystems in subsequent changes.Signed-off-by: Marco Elver Signed-off-by: Peter Zijlstra (Intel) Link: https://patch.msgid.link/20251219154418.3592607-26-elver@google.com List of files: /linux/scripts/Makefile.context-analysis

3269701cb25662ae8a9771a864201116626adb50 - compiler-context-analysis: Add infrastructure for Context Analysis with Clang

Fri, 19 Dec 2025 16:39:51 +0100

compiler-context-analysis: Add infrastructure for Context Analysis with ClangContext Analysis is a language extension, which enables staticallychecking that required contexts are active (or inactive), by acquiringand releasing user-definable "context locks". An obvious application islock-safety checking for the kernel's various synchronization primitives(each of which represents a "context lock"), and checking that lockingrules are not violated.Clang originally called the feature "Thread Safety Analysis" [1]. Thiswas later changed and the feature became more flexible, gaining theability to define custom "capabilities". Its foundations can be found in"Capability Systems" [2], used to specify the permissibility ofoperations to depend on some "capability" being held (or not held).Because the feature is not just able to express "capabilities" relatedto synchronization primitives, and "capability" is already overloaded inthe kernel, the naming chosen for the kernel departs from Clang's"Thread Safety" and "capability" nomenclature; we refer to the featureas "Context Analysis" to avoid confusion. The internal implementationstill makes references to Clang's terminology in a few places, such as`-Wthread-safety` being the warning option that also still appears indiagnostic messages. [1] https://clang.llvm.org/docs/ThreadSafetyAnalysis.html [2] https://www.cs.cornell.edu/talc/papers/capabilities.pdfSee more details in the kernel-doc documentation added in this andsubsequent changes.Clang version 22+ is required.[peterz: disable the thing for __CHECKER__ builds]Signed-off-by: Marco Elver Signed-off-by: Peter Zijlstra (Intel) Link: https://patch.msgid.link/20251219154418.3592607-3-elver@google.com List of files: /linux/scripts/Makefile.context-analysis