linux-kernel - Re: [PATCH v2 00/12 6.6.y] Backport minmax.h updates from v6.17-rc7

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: <2025093045-proclaim-backwash-3b41@gregkh>
Date: Tue, 30 Sep 2025 16:04:52 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Eliav Farber <farbere@...zon.com>
Cc: sashal@...nel.org, mario.limonciello@....com, lijo.lazar@....com,
	David.Laight@...lab.com, arnd@...nel.org,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH v2 00/12 6.6.y] Backport minmax.h updates from v6.17-rc7

On Mon, Sep 29, 2025 at 05:17:21PM +0000, Eliav Farber wrote:
> This series backports 15 patches to update minmax.h in the 6.6.y branch,
> aligning it with v6.17-rc7.
> 
> The ultimate goal is to synchronize all longterm branches so that they
> include the full set of minmax.h changes.
> 
> The key motivation is to bring in commit d03eba99f5bf ("minmax: allow
> min()/max()/clamp() if the arguments have the same signedness"), which
> is missing in older kernels.
> 
> In mainline, this change enables min()/max()/clamp() to accept mixed
> argument types, provided both have the same signedness. Without it,
> backported patches that use these forms may trigger compiler warnings,
> which escalate to build failures when -Werror is enabled.

All now queued up, thanks!

greg k-h