linux-kernel - Re: [PATCH cmpxchg 08/14] parisc: add u16 support to cmpxchg()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=whwbdbNXeJ0m+YZqZcxKPD3v4dbcPVCd6gP7YkwCM=X7w@mail.gmail.com>
Date: Mon, 8 Apr 2024 13:10:40 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "Paul E. McKenney" <paulmck@...nel.org>
Cc: linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org, elver@...gle.com, 
	akpm@...ux-foundation.org, tglx@...utronix.de, peterz@...radead.org, 
	dianders@...omium.org, pmladek@...e.com, Arnd Bergmann <arnd@...db.de>, 
	Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH cmpxchg 08/14] parisc: add u16 support to cmpxchg()

On Mon, 8 Apr 2024 at 10:50, Paul E. McKenney <paulmck@...nel.org> wrote:
>
> And get rid of manual truncation down to u8, etc. in there - the
> only reason for those is to avoid bogus warnings about constant
> truncation from sparse, and those are easy to avoid by turning
> that switch into conditional expression.

I support the use of the conditional, but why add the 16-bit case when
it turns out we don't want it after all?

                 Linus