From: Thomas Gleixner <[email protected]>
To: kernel test robot <[email protected]>
Cc: [email protected],
Ammar Faizi <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
"David S. Miller" <[email protected]>,
[email protected], Peter Zijlstra <[email protected]>,
Will Deacon <[email protected]>,
David Howells <[email protected]>
Subject: Re: [ammarfaizi2-block:tglx/devel/rcuref 2/3] arch/sparc/include/asm/cmpxchg_64.h:161:55: sparse: sparse: cast truncates bits from constant value (ffffffffe0000000 becomes 0)
Date: Wed, 01 Mar 2023 22:57:57 +0100 [thread overview]
Message-ID: <87k000kuca.ffs@tglx> (raw)
In-Reply-To: <[email protected]>
On Wed, Mar 01 2023 at 15:48, kernel test robot wrote:
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <[email protected]>
> | Link: https://lore.kernel.org/oe-kbuild-all/[email protected]/
>
> sparse warnings: (new ones prefixed by >>)
> lib/rcuref.c: note: in included file (through arch/sparc/include/asm/cmpxchg.h, arch/sparc/include/asm/atomic_64.h, arch/sparc/include/asm/atomic.h, ...):
>>> arch/sparc/include/asm/cmpxchg_64.h:161:55: sparse: sparse: cast truncates bits from constant value (ffffffffe0000000 becomes 0)
Cute. The constant value is 0xFFFF FFFF E000 0000. So how is that implicit down
cast causing it to become 0? Sparse is silly.
But that aside, the sparc64 cmpxchg() code is silly as well:
> vim +161 arch/sparc/include/asm/cmpxchg_64.h
>
> d550bbd40c0e10 David Howells 2012-03-28 155
> d550bbd40c0e10 David Howells 2012-03-28 156 static inline unsigned long
> d550bbd40c0e10 David Howells 2012-03-28 157 __cmpxchg(volatile void *ptr, unsigned long old, unsigned long new, int size)
> d550bbd40c0e10 David Howells 2012-03-28 158 {
> d550bbd40c0e10 David Howells 2012-03-28 159 switch (size) {
> a12ee2349312d7 Babu Moger 2017-05-24 160 case 1:
> a12ee2349312d7 Babu Moger 2017-05-24 @161 return __cmpxchg_u8(ptr, old, new);
> d550bbd40c0e10 David Howells 2012-03-28 162 case 4:
> d550bbd40c0e10 David Howells 2012-03-28 163 return __cmpxchg_u32(ptr, old, new);
> d550bbd40c0e10 David Howells 2012-03-28 164 case 8:
> d550bbd40c0e10 David Howells 2012-03-28 165 return __cmpxchg_u64(ptr, old, new);
> d550bbd40c0e10 David Howells 2012-03-28 166 }
> d550bbd40c0e10 David Howells 2012-03-28 167 __cmpxchg_called_with_bad_pointer();
> d550bbd40c0e10 David Howells 2012-03-28 168 return old;
> d550bbd40c0e10 David Howells 2012-03-28 169 }
> d550bbd40c0e10 David Howells 2012-03-28 170
which gets invoked via:
#define arch_cmpxchg(ptr,o,n) \
({ \
__typeof__(*(ptr)) _o_ = (o); \
__typeof__(*(ptr)) _n_ = (n); \
(__typeof__(*(ptr))) __cmpxchg((ptr), (unsigned long)_o_, \
(unsigned long)_n_, sizeof(*(ptr))); \
})
and then ends up in
static inline unsigned long __cmpxchg_u32(volatile int *m, int old, int new)
I'm sure a sparse build of sparc64 is full of those warnings. This just
happens to add one to the existing noise.
Oh well.
tglx
prev parent reply other threads:[~2023-03-01 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 7:48 [ammarfaizi2-block:tglx/devel/rcuref 2/3] arch/sparc/include/asm/cmpxchg_64.h:161:55: sparse: sparse: cast truncates bits from constant value (ffffffffe0000000 becomes 0) kernel test robot
2023-03-01 21:57 ` Thomas Gleixner [this message]
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=87k000kuca.ffs@tglx \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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