From: "Paul E. McKenney" <paulmck@kernel.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
"kernel test robot" <lkp@intel.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>
Subject: Re: [PATCH] ia64: fix sparse warnings with cmpxchg() & xchg()
Date: Sun, 5 Jun 2022 12:58:25 -0700 [thread overview]
Message-ID: <20220605195825.GW1790663@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20220605160738.79736-1-luc.vanoostenryck@gmail.com>
On Sun, Jun 05, 2022 at 06:07:38PM +0200, Luc Van Oostenryck wrote:
> On IA64, new sparse's warnings where issued after fixing
> some __rcu annotations in kernel/bpf/.
>
> These new warnings are false positives and appear on IA64 because
> on this architecture, the macros for cmpxchg() and xchg() make
> casts that ignore sparse annotations.
>
> This patch contains the minimal patch to fix this issue:
> adding a missing cast and some missing '__force'.
>
> Link: https://lore.kernel.org/r/20220601120013.bq5a3ynbkc3hngm5@mail
> Reported-by: kernel test robot <lkp@intel.com>
> Cc: Toke Høiland-Jørgensen <toke@redhat.com>
> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Looks good to me!
Acked-by: Paul E. McKenney <paulmck@kernel.org>
> ---
>
> Note: This patch is only compile tested on defconfig. The corresponding
> binary is unchanged (except some .rodata with the kernel version)
> as it should be.
>
> arch/ia64/include/uapi/asm/cmpxchg.h | 28 ++++++++++++++--------------
> 1 file changed, 14 insertions(+), 14 deletions(-)
>
> diff --git a/arch/ia64/include/uapi/asm/cmpxchg.h b/arch/ia64/include/uapi/asm/cmpxchg.h
> index 2c2f3cfeaa77..ca2e02685343 100644
> --- a/arch/ia64/include/uapi/asm/cmpxchg.h
> +++ b/arch/ia64/include/uapi/asm/cmpxchg.h
> @@ -33,24 +33,24 @@ extern void ia64_xchg_called_with_bad_pointer(void);
> \
> switch (size) { \
> case 1: \
> - __xchg_result = ia64_xchg1((__u8 *)ptr, x); \
> + __xchg_result = ia64_xchg1((__u8 __force *)ptr, x); \
> break; \
> \
> case 2: \
> - __xchg_result = ia64_xchg2((__u16 *)ptr, x); \
> + __xchg_result = ia64_xchg2((__u16 __force *)ptr, x); \
> break; \
> \
> case 4: \
> - __xchg_result = ia64_xchg4((__u32 *)ptr, x); \
> + __xchg_result = ia64_xchg4((__u32 __force *)ptr, x); \
> break; \
> \
> case 8: \
> - __xchg_result = ia64_xchg8((__u64 *)ptr, x); \
> + __xchg_result = ia64_xchg8((__u64 __force *)ptr, x); \
> break; \
> default: \
> ia64_xchg_called_with_bad_pointer(); \
> } \
> - __xchg_result; \
> + (__typeof__ (*(ptr)) __force) __xchg_result; \
> })
>
> #ifndef __KERNEL__
> @@ -76,42 +76,42 @@ extern long ia64_cmpxchg_called_with_bad_pointer(void);
> \
> switch (size) { \
> case 1: \
> - _o_ = (__u8) (long) (old); \
> + _o_ = (__u8) (long __force) (old); \
> break; \
> case 2: \
> - _o_ = (__u16) (long) (old); \
> + _o_ = (__u16) (long __force) (old); \
> break; \
> case 4: \
> - _o_ = (__u32) (long) (old); \
> + _o_ = (__u32) (long __force) (old); \
> break; \
> case 8: \
> - _o_ = (__u64) (long) (old); \
> + _o_ = (__u64) (long __force) (old); \
> break; \
> default: \
> break; \
> } \
> switch (size) { \
> case 1: \
> - _r_ = ia64_cmpxchg1_##sem((__u8 *) ptr, new, _o_); \
> + _r_ = ia64_cmpxchg1_##sem((__u8 __force *) ptr, new, _o_); \
> break; \
> \
> case 2: \
> - _r_ = ia64_cmpxchg2_##sem((__u16 *) ptr, new, _o_); \
> + _r_ = ia64_cmpxchg2_##sem((__u16 __force *) ptr, new, _o_); \
> break; \
> \
> case 4: \
> - _r_ = ia64_cmpxchg4_##sem((__u32 *) ptr, new, _o_); \
> + _r_ = ia64_cmpxchg4_##sem((__u32 __force *) ptr, new, _o_); \
> break; \
> \
> case 8: \
> - _r_ = ia64_cmpxchg8_##sem((__u64 *) ptr, new, _o_); \
> + _r_ = ia64_cmpxchg8_##sem((__u64 __force *) ptr, new, _o_); \
> break; \
> \
> default: \
> _r_ = ia64_cmpxchg_called_with_bad_pointer(); \
> break; \
> } \
> - (__typeof__(old)) _r_; \
> + (__typeof__(old) __force) _r_; \
> })
>
> #define cmpxchg_acq(ptr, o, n) \
> --
> 2.36.1
>
next prev parent reply other threads:[~2022-06-05 19:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 12:30 kernel/bpf/devmap.c:1030:40: sparse: sparse: cast removes address space '__rcu' of expression kernel test robot
2022-05-23 10:30 ` Toke Høiland-Jørgensen
2022-05-24 20:51 ` Paul E. McKenney
2022-06-01 0:38 ` Luc Van Oostenryck
2022-06-01 10:26 ` Toke Høiland-Jørgensen
2022-06-01 12:00 ` Luc Van Oostenryck
2022-06-05 16:07 ` [PATCH] ia64: fix sparse warnings with cmpxchg() & xchg() Luc Van Oostenryck
2022-06-05 19:58 ` Paul E. McKenney [this message]
2022-06-06 7:53 ` Toke Høiland-Jørgensen
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=20220605195825.GW1790663@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luc.vanoostenryck@gmail.com \
--cc=toke@redhat.com \
/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).