linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Finn Thain <fthain@linux-m68k.org>
To: Peter Zijlstra <peterz@infradead.org>, Will Deacon <will@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Boqun Feng <boqun.feng@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Mark Rutland <mark.rutland@arm.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k@vger.kernel.org
Subject: [RFC v2 3/3] atomic: Add alignment check to instrumented atomic operations
Date: Sun, 14 Sep 2025 10:45:29 +1000	[thread overview]
Message-ID: <e5a38b0ccf2d37185964a69b6e8657c992966ff7.1757810729.git.fthain@linux-m68k.org> (raw)
In-Reply-To: <cover.1757810729.git.fthain@linux-m68k.org>

From: Peter Zijlstra <peterz@infradead.org>

Add a Kconfig option for debug builds which logs a warning when an
instrumented atomic operation takes place at some location that isn't
a long word boundary. Some platforms don't trap for this.

Link: https://lore.kernel.org/lkml/20250901093600.GF4067720@noisy.programming.kicks-ass.net/
---
This patch differs slightly from Peter's code which checked for natural
alignment.
---
 include/linux/instrumented.h |  4 ++++
 lib/Kconfig.debug            | 10 ++++++++++
 2 files changed, 14 insertions(+)

diff --git a/include/linux/instrumented.h b/include/linux/instrumented.h
index 711a1f0d1a73..55f5685971a1 100644
--- a/include/linux/instrumented.h
+++ b/include/linux/instrumented.h
@@ -7,6 +7,7 @@
 #ifndef _LINUX_INSTRUMENTED_H
 #define _LINUX_INSTRUMENTED_H
 
+#include <linux/bug.h>
 #include <linux/compiler.h>
 #include <linux/kasan-checks.h>
 #include <linux/kcsan-checks.h>
@@ -67,6 +68,7 @@ static __always_inline void instrument_atomic_read(const volatile void *v, size_
 {
 	kasan_check_read(v, size);
 	kcsan_check_atomic_read(v, size);
+	WARN_ON_ONCE(IS_ENABLED(CONFIG_DEBUG_ATOMIC) && ((unsigned long)v & (sizeof(long) - 1)));
 }
 
 /**
@@ -81,6 +83,7 @@ static __always_inline void instrument_atomic_write(const volatile void *v, size
 {
 	kasan_check_write(v, size);
 	kcsan_check_atomic_write(v, size);
+	WARN_ON_ONCE(IS_ENABLED(CONFIG_DEBUG_ATOMIC) && ((unsigned long)v & (sizeof(long) - 1)));
 }
 
 /**
@@ -95,6 +98,7 @@ static __always_inline void instrument_atomic_read_write(const volatile void *v,
 {
 	kasan_check_write(v, size);
 	kcsan_check_atomic_read_write(v, size);
+	WARN_ON_ONCE(IS_ENABLED(CONFIG_DEBUG_ATOMIC) && ((unsigned long)v & (sizeof(long) - 1)));
 }
 
 /**
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index ebe33181b6e6..d82626b7d6be 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -1363,6 +1363,16 @@ config DEBUG_PREEMPT
 	  depending on workload as it triggers debugging routines for each
 	  this_cpu operation. It should only be used for debugging purposes.
 
+config DEBUG_ATOMIC
+	bool "Debug atomic variables"
+	depends on DEBUG_KERNEL
+	help
+	  If you say Y here then the kernel will add a runtime alignment check
+	  to atomic accesses. Useful for architectures that do not have trap on
+	  mis-aligned access.
+
+	  This option has potentially significant overhead.
+
 menu "Lock Debugging (spinlocks, mutexes, etc...)"
 
 config LOCK_DEBUGGING_SUPPORT
-- 
2.49.1


  parent reply	other threads:[~2025-09-14  0:59 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-14  0:45 [RFC v2 0/3] Align atomic storage Finn Thain
2025-09-14  0:45 ` [RFC v2 2/3] atomic: Specify alignment for atomic_t and atomic64_t Finn Thain
2025-09-15  7:13   ` Geert Uytterhoeven
2025-09-15  7:35   ` Arnd Bergmann
2025-09-15  8:06     ` Peter Zijlstra
2025-09-15  9:26     ` Finn Thain
2025-09-15  9:29       ` Arnd Bergmann
2025-09-22  7:06   ` Geert Uytterhoeven
2025-09-22  8:16     ` Finn Thain
2025-09-22  9:29       ` Geert Uytterhoeven
2025-09-22 15:21       ` Arnd Bergmann
2025-09-23  6:28         ` Finn Thain
2025-09-23  6:41           ` Arnd Bergmann
2025-09-23  8:05             ` Finn Thain
2025-09-23 19:11               ` Arnd Bergmann
2025-09-30  2:18           ` Finn Thain
2025-09-30  6:35             ` Arnd Bergmann
2025-10-01  1:03               ` Finn Thain
2025-10-01  6:44                 ` Arnd Bergmann
2025-10-06  9:25                   ` Finn Thain
2025-10-06  9:25               ` Finn Thain
2025-10-06 10:07                 ` Arnd Bergmann
2025-10-06 10:22                   ` Peter Zijlstra
2025-10-06 11:09                     ` Arnd Bergmann
2025-10-06  9:37               ` Peter Zijlstra
2025-09-30  7:41             ` Geert Uytterhoeven
2025-10-01  1:46               ` Finn Thain
2025-10-01  7:08                 ` Geert Uytterhoeven
2025-09-14  0:45 ` [RFC v2 1/3] documentation: Discourage alignment assumptions Finn Thain
2025-09-14  0:45 ` Finn Thain [this message]
2025-09-15  8:00   ` [RFC v2 3/3] atomic: Add alignment check to instrumented atomic operations Peter Zijlstra
2025-09-15  9:38     ` Finn Thain
2025-09-15 10:06       ` Peter Zijlstra
2025-09-15 10:37         ` Finn Thain
2025-09-15 11:20           ` Arnd Bergmann
2025-09-16  0:16             ` Finn Thain
2025-09-16 10:10               ` Geert Uytterhoeven
2025-09-17  1:23                 ` Finn Thain
2025-09-16 12:37               ` Arnd Bergmann
2025-09-16 21:38                 ` Brad Boyer
2025-09-17 16:54                   ` Andreas Schwab
2025-09-17  2:14                 ` Finn Thain
2025-09-22 15:49                   ` Arnd Bergmann
2025-09-23  6:39                     ` Finn Thain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e5a38b0ccf2d37185964a69b6e8657c992966ff7.1757810729.git.fthain@linux-m68k.org \
    --to=fthain@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=boqun.feng@gmail.com \
    --cc=corbet@lwn.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=peterz@infradead.org \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).