linux-kernel - Re: [PATCH 00/10] sparc64: Fix CPU online bug and warning fixes

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 for Android: free password hash cracker in your pocket

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

Message-Id: <4e57929b-1539-4a25-ab05-a2a9e04ecc1d@app.fastmail.com>
Date: Sat, 30 Mar 2024 11:19:37 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Sam Ravnborg" <sam@...nborg.org>,
 "Andreas Larsson" <andreas@...sler.com>,
 "David S . Miller" <davem@...emloft.net>, sparclinux@...r.kernel.org
Cc: "Nick Bowler" <nbowler@...conx.ca>, linux-kernel@...r.kernel.org,
 "Atish Patra" <atish.patra@...cle.com>, stable@...r.kernel.org,
 "Bob Picco" <bob.picco@...cle.com>, "Vijay Kumar" <vijay.ac.kumar@...cle.com>
Subject: Re: [PATCH 00/10] sparc64: Fix CPU online bug and warning fixes

On Sat, Mar 30, 2024, at 10:57, Sam Ravnborg via B4 Relay wrote:
> Nick Bowler reported that sparc64 failed to bring all his CPU's online,
> and that turned out to be an easy fix.
>
> The sparc64 build was rather noisy with a lot of warnings which had
> irritated me enough to go ahead and fix them.
> With this set of patches my arch/sparc/ is almost warning free for
> all{no,yes,mod}config + defconfig builds.

Patches 1-9 look good to me,

Acked-by: Arnd Bergmann <arnd@...db.de>

> There is one warning about "clone3 not implemented", which I have ignored.
>
> The warning fixes hides the fact that sparc64 is not yet y2038 prepared,
> and it would be preferable if someone knowledgeable would fix this
> poperly.

The clone3 bug has been around for ages, it's probably not even that
hard to fix and just needs a little bit of testing.

If anyone wants to work on the time64 support for the vdso, I can
explain the details for how it's done.

Both of these are real bugs that should be addressed, unlike
the other warning fixes that are mostly cosmetic aside from
allowing the build with CONFIG_WERROR=y.

     Arnd