linux-kernel - Re: [PATCH] xfs: replace min & max with clamp() in xfs_max_open

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: <xpuse6544mmww24s7hqtgwcky2wyc5amykfdftfqeb2ghaqejy@6zj65eavbm6x>
Date: Tue, 15 Jul 2025 11:49:53 +0200
From: Carlos Maiolino <cem@...nel.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: John Garry <john.g.garry@...cle.com>, 
	George Hu <integral@...hlinux.org>, linux-xfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] xfs: replace min & max with clamp() in
 xfs_max_open_zones()

On Mon, Jul 14, 2025 at 03:59:27AM -0700, Christoph Hellwig wrote:
> On Mon, Jul 14, 2025 at 08:58:59AM +0100, John Garry wrote:
> > > @@ -1133,9 +1133,7 @@ xfs_max_open_zones(
> > >   	/*
> > >   	 * Cap the max open limit to 1/4 of available space
> > >   	 */
> >
> > Maybe you can keep this comment, but it was pretty much describing the code
> > and not explaining the rationale.
> 
> Let me send an incremental patch to explain the rational as long as I
> can still remember it :)

Sounds good, I'll wait and merge both together.

> 
>