linux-kernel - Re: [PATCH v3 00/14] tools/nolibc: always use 64-bit time-related types

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] [day] [month] [year] [list]

Message-Id: <098abb99-bfa7-43c5-8a54-556ccd4f3448@app.fastmail.com>
Date: Mon, 22 Dec 2025 10:39:33 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: Thomas Weißschuh <linux@...ssschuh.net>,
 "Willy Tarreau" <w@....eu>, shuah <shuah@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH v3 00/14] tools/nolibc: always use 64-bit time-related types

On Sat, Dec 20, 2025, at 14:55, Thomas Weißschuh wrote:
> nolibc currently uses 32-bit types for various APIs. These are
> problematic as their reduced value range can lead to truncated values.
>
> Intended for 6.19.
>
> Signed-off-by: Thomas Weißschuh <linux@...ssschuh.net>
> ---
> Changes in v3:
> - Only use _Static_assert() where available
> - Link to v2: 
> https://lore.kernel.org/r/20251122-nolibc-uapi-types-v2-0-b814a43654f5@weissschuh.net

I looked at each patch again, and I this looks great to me!

Whole series

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