From: "Arnd Bergmann" <arnd@arndb.de>
To: "Finn Thain" <fthain@linux-m68k.org>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Will Deacon" <will@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Mark Rutland" <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-m68k@vger.kernel.org, "Lance Yang" <lance.yang@linux.dev>
Subject: Re: [RFC v2 2/3] atomic: Specify alignment for atomic_t and atomic64_t
Date: Mon, 06 Oct 2025 12:07:24 +0200 [thread overview]
Message-ID: <d9e3f41e-d152-4382-bb99-7b134ff9f26f@app.fastmail.com> (raw)
In-Reply-To: <257a045a-f39d-8565-608f-f01f7914be21@linux-m68k.org>
On Mon, Oct 6, 2025, at 11:25, Finn Thain wrote:
> On Tue, 30 Sep 2025, Arnd Bergmann wrote:
>> On Tue, Sep 30, 2025, at 04:18, Finn Thain wrote:
>>
>> Since there is nothing telling the compiler that the 'old' argument to
>> atomic*_try_cmpcxchg() needs to be naturally aligned, maybe that check
>> should be changed to only test for the ABI-guaranteed alignment? I think
>> that would still be needed on x86-32.
>>
>> diff --git a/include/linux/atomic/atomic-instrumented.h b/include/linux/atomic/atomic-instrumented.h
>> index 9409a6ddf3e0..e57763a889bd 100644
>> --- a/include/linux/atomic/atomic-instrumented.h
>> +++ b/include/linux/atomic/atomic-instrumented.h
>> @@ -1276,7 +1276,7 @@ atomic_try_cmpxchg(atomic_t *v, int *old, int new)
>> {
>> kcsan_mb();
>> instrument_atomic_read_write(v, sizeof(*v));
>> - instrument_atomic_read_write(old, sizeof(*old));
>> + instrument_atomic_read_write(old, alignof(*old));
>> return raw_atomic_try_cmpxchg(v, old, new);
>> }
>>
>
> In the same file, we have:
>
> #define try_cmpxchg(ptr, oldp, ...) \
> ({ \
> typeof(ptr) __ai_ptr = (ptr); \
> typeof(oldp) __ai_oldp = (oldp); \
> kcsan_mb(); \
> instrument_atomic_read_write(__ai_ptr, sizeof(*__ai_ptr)); \
> instrument_read_write(__ai_oldp, sizeof(*__ai_oldp)); \
> raw_try_cmpxchg(__ai_ptr, __ai_oldp, __VA_ARGS__); \
> })
>
> In try_cmpxchg(), unlike atomic_try_cmpxchg(), the 'old' parameter is
> checked by instrument_read_write() instead of
> instrument_atomic_read_write(), which suggests a different patch.
Right, we still need the effect of instrument_read_write() for
kasan/kcsan sanitizing with the correct size, only the alignment
check from the instrument_atomic_read_write() is wrong here
here.
It looks like Mark Rutland fixed the try_cmpxchg() function this
way in commit ec570320b09f ("locking/atomic: Correct (cmp)xchg()
instrumentation"), but for some reason we still have the wrong
annotation on the atomic_try_cmpxchg() helpers.
> This header is generated by a script so the change below would be more
> complicated in practice.
>
> diff --git a/include/linux/atomic/atomic-instrumented.h
> b/include/linux/atomic/atomic-instrumented.h
> index 9409a6ddf3e0..ce3890bcd903 100644
> --- a/include/linux/atomic/atomic-instrumented.h
> +++ b/include/linux/atomic/atomic-instrumented.h
> @@ -1276,7 +1276,7 @@ atomic_try_cmpxchg(atomic_t *v, int *old, int new)
> {
> kcsan_mb();
> instrument_atomic_read_write(v, sizeof(*v));
> - instrument_atomic_read_write(old, sizeof(*old));
> + instrument_read_write(old, sizeof(*old));
> return raw_atomic_try_cmpxchg(v, old, new);
> }
This looks good to me.
Mark, I've tried to modify your script to produce that output,
the output looks correct to me, but it makes the script more
complex than I liked and I'm not sure that matching on
"${type}"="p" is the best way to check for this.
Maybe you can come up with a version that is clearer or more robust.
Arnd
diff --git a/scripts/atomic/gen-atomic-instrumented.sh b/scripts/atomic/gen-atomic-instrumented.sh
index 592f3ec89b5f..9c1d53f81eb2 100755
--- a/scripts/atomic/gen-atomic-instrumented.sh
+++ b/scripts/atomic/gen-atomic-instrumented.sh
@@ -12,7 +12,7 @@ gen_param_check()
local arg="$1"; shift
local type="${arg%%:*}"
local name="$(gen_param_name "${arg}")"
- local rw="write"
+ local rw="atomic_write"
case "${type#c}" in
i) return;;
@@ -20,14 +20,17 @@ gen_param_check()
if [ ${type#c} != ${type} ]; then
# We don't write to constant parameters.
- rw="read"
+ rw="atomic_read"
+ elif [ "${type}" = "p" ] ; then
+ # The "old" argument in try_cmpxchg() gets accessed non-atomically
+ rw="read_write"
elif [ "${meta}" != "s" ]; then
# An atomic RMW: if this parameter is not a constant, and this atomic is
# not just a 's'tore, this parameter is both read from and written to.
- rw="read_write"
+ rw="atomic_read_write"
fi
- printf "\tinstrument_atomic_${rw}(${name}, sizeof(*${name}));\n"
+ printf "\tinstrument_${rw}(${name}, sizeof(*${name}));\n"
}
#gen_params_checks(meta, arg...)
next prev parent reply other threads:[~2025-10-06 10:08 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 [this message]
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 ` [RFC v2 3/3] atomic: Add alignment check to instrumented atomic operations Finn Thain
2025-09-15 8:00 ` 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=d9e3f41e-d152-4382-bb99-7b134ff9f26f@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=lance.yang@linux.dev \
--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).