From: David Laight <david.laight.linux@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Eliav Farber <farbere@amazon.com>,
dave.hansen@linux.intel.com, peterz@infradead.org,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
x86@kernel.org, hpa@zytor.com, james.morse@arm.com,
rric@kernel.org, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, sean@poorly.run, jdelvare@suse.com,
linux@roeck-us.net, linus.walleij@linaro.org,
dmitry.torokhov@gmail.com, maz@kernel.org, wens@csie.org,
jernej.skrabec@gmail.com, agk@redhat.com, snitzer@redhat.com,
dm-devel@redhat.com, davem@davemloft.net, kuba@kernel.org,
mcoquelin.stm32@gmail.com, krzysztof.kozlowski@canonical.com,
malattia@linux.it, hdegoede@redhat.com, mgross@linux.intel.com,
jejb@linux.ibm.com, martin.petersen@oracle.com,
sakari.ailus@linux.intel.com, clm@fb.com, josef@toxicpanda.com,
dsterba@suse.com, jack@suse.com, tytso@mit.edu,
adilger.kernel@dilger.ca, dushistov@mail.ru,
luc.vanoostenryck@gmail.com, rostedt@goodmis.org,
pmladek@suse.com, senozhatsky@chromium.org,
andriy.shevchenko@linux.intel.com, linux@rasmusvillemoes.dk,
minchan@kernel.org, ngupta@vflare.org, akpm@linux-foundation.org,
yoshfuji@linux-ipv6.org, dsahern@kernel.org, pablo@netfilter.org,
kadlec@netfilter.org, fw@strlen.de, jmaloy@redhat.com,
ying.xue@windriver.com, shuah@kernel.org, willy@infradead.org,
sashal@kernel.org, quic_akhilpo@quicinc.com,
ruanjinjie@huawei.com, David.Laight@aculab.com,
herve.codina@bootlin.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-um@lists.infradead.org,
linux-edac@vger.kernel.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org, linux-hwmon@vger.kernel.org,
linux-input@vger.kernel.org, linux-sunxi@lists.linux.dev,
linux-media@vger.kernel.org, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
platform-driver-x86@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-staging@lists.linux.dev, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-sparse@vger.kernel.org,
linux-mm@kvack.org, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org, tipc-discussion@lists.sourceforge.net,
linux-kselftest@vger.kernel.org, stable@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: [PATCH v2 07/19 5.15.y] minmax: simplify and clarify min_t()/max_t() implementation
Date: Mon, 6 Oct 2025 21:35:03 +0100 [thread overview]
Message-ID: <20251006213242.3462e746@pumpkin> (raw)
In-Reply-To: <2025100648-capable-register-101b@gregkh>
On Mon, 6 Oct 2025 12:47:45 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:
(I've had to trim the 'To' list to send this...)
> On Fri, Oct 03, 2025 at 12:59:54PM +0000, Eliav Farber wrote:
> > From: Linus Torvalds <torvalds@linux-foundation.org>
> >
> > [ Upstream commit 017fa3e89187848fd056af757769c9e66ac3e93d ]
> >
> > This simplifies the min_t() and max_t() macros by no longer making them
> > work in the context of a C constant expression.
> >
> > That means that you can no longer use them for static initializers or
> > for array sizes in type definitions, but there were only a couple of
> > such uses, and all of them were converted (famous last words) to use
> > MIN_T/MAX_T instead.
> >
> > Cc: David Laight <David.Laight@aculab.com>
> > Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> > Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> > Signed-off-by: Eliav Farber <farbere@amazon.com>
>
> Eliav, your testing infrastructure needs some work, this patch breaks
> the build on this kernel tree:
>
> In file included from ./include/linux/kernel.h:16,
> from ./include/linux/list.h:9,
> from ./include/linux/wait.h:7,
> from ./include/linux/wait_bit.h:8,
> from ./include/linux/fs.h:6,
> from fs/erofs/internal.h:10,
> from fs/erofs/zdata.h:9,
> from fs/erofs/zdata.c:6:
> fs/erofs/zdata.c: In function ‘z_erofs_decompress_pcluster’:
> fs/erofs/zdata.h:185:61: error: ISO C90 forbids variable length array ‘pages_onstack’ [-Werror=vla]
> 185 | min_t(unsigned int, THREAD_SIZE / 8 / sizeof(struct page *), 96U)
> | ^~~~
That constant seems to get (renamed and) changed to 32 in a later patch.
I'm not sure of the rational for the min() at all.
I think THREAD_SIZE is the size of the kernel stack? Or at least related to it.
The default seems to be 8k on x86-64 and 4k or 8k on i386.
So it is pretty much always going to be 96.
Linus added MIN() that can be used for array sizes.
But I'd guess this could just be changed to 32 - need to ask the erofs guys.
David
> ./include/linux/minmax.h:49:23: note: in definition of macro ‘__cmp_once_unique’
> 49 | ({ type ux = (x); type uy = (y); __cmp(op, ux, uy); })
> | ^
> ./include/linux/minmax.h:164:27: note: in expansion of macro ‘__cmp_once’
> 164 | #define min_t(type, x, y) __cmp_once(min, type, x, y)
> | ^~~~~~~~~~
> fs/erofs/zdata.h:185:9: note: in expansion of macro ‘min_t’
> 185 | min_t(unsigned int, THREAD_SIZE / 8 / sizeof(struct page *), 96U)
> | ^~~~~
> fs/erofs/zdata.c:847:36: note: in expansion of macro ‘Z_EROFS_VMAP_ONSTACK_PAGES’
> 847 | struct page *pages_onstack[Z_EROFS_VMAP_ONSTACK_PAGES];
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
>
>
> I'll drop this whole series, please do a bit more testing before sending
> out a new version.
>
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2025-10-06 20:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 12:59 [PATCH v2 00/19 5.15.y] Backport minmax.h updates from v6.17-rc7 Eliav Farber
2025-10-03 12:59 ` [PATCH v2 01/19 5.15.y] minmax: add in_range() macro Eliav Farber
2025-10-03 12:59 ` [PATCH v2 02/19 5.15.y] minmax: Introduce {min,max}_array() Eliav Farber
2025-10-03 12:59 ` [PATCH v2 03/19 5.15.y] minmax: deduplicate __unconst_integer_typeof() Eliav Farber
2025-10-03 12:59 ` [PATCH v2 04/19 5.15.y] minmax: fix indentation of __cmp_once() and __clamp_once() Eliav Farber
2025-10-03 12:59 ` [PATCH v2 05/19 5.15.y] minmax: avoid overly complicated constant expressions in VM code Eliav Farber
2025-10-03 12:59 ` [PATCH v2 06/19 5.15.y] minmax: add a few more MIN_T/MAX_T users Eliav Farber
2025-10-03 12:59 ` [PATCH v2 07/19 5.15.y] minmax: simplify and clarify min_t()/max_t() implementation Eliav Farber
2025-10-06 10:47 ` Greg KH
2025-10-06 20:35 ` David Laight [this message]
2025-10-07 20:43 ` Farber, Eliav
2025-10-03 12:59 ` [PATCH v2 08/19 5.15.y] minmax: make generic MIN() and MAX() macros available everywhere Eliav Farber
2025-10-03 12:59 ` [PATCH v2 09/19 5.15.y] minmax: don't use max() in situations that want a C constant expression Eliav Farber
2025-10-03 12:59 ` [PATCH v2 10/19 5.15.y] minmax: simplify min()/max()/clamp() implementation Eliav Farber
2025-10-03 12:59 ` [PATCH v2 11/19 5.15.y] minmax: improve macro expansion and type checking Eliav Farber
2025-10-03 12:59 ` [PATCH v2 12/19 5.15.y] minmax: fix up min3() and max3() too Eliav Farber
2025-10-03 13:00 ` [PATCH v2 13/19 5.15.y] minmax.h: add whitespace around operators and after commas Eliav Farber
2025-10-03 13:00 ` [PATCH v2 14/19 5.15.y] minmax.h: update some comments Eliav Farber
2025-10-03 13:00 ` [PATCH v2 15/19 5.15.y] minmax.h: reduce the #define expansion of min(), max() and clamp() Eliav Farber
2025-10-03 13:00 ` [PATCH v2 16/19 5.15.y] minmax.h: use BUILD_BUG_ON_MSG() for the lo < hi test in clamp() Eliav Farber
2025-10-03 13:00 ` [PATCH v2 17/19 5.15.y] minmax.h: move all the clamp() definitions after the min/max() ones Eliav Farber
2025-10-03 13:00 ` [PATCH v2 18/19 5.15.y] minmax.h: simplify the variants of clamp() Eliav Farber
2025-10-03 13:00 ` [PATCH v2 19/19 5.15.y] minmax.h: remove some #defines that are only expanded once Eliav Farber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251006213242.3462e746@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=David.Laight@aculab.com \
--cc=adilger.kernel@dilger.ca \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=clm@fb.com \
--cc=coreteam@netfilter.org \
--cc=daniel@ffwll.ch \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dm-devel@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dsahern@kernel.org \
--cc=dsterba@suse.com \
--cc=dushistov@mail.ru \
--cc=farbere@amazon.com \
--cc=freedreno@lists.freedesktop.org \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=herve.codina@bootlin.com \
--cc=hpa@zytor.com \
--cc=jack@suse.com \
--cc=james.morse@arm.com \
--cc=jdelvare@suse.com \
--cc=jejb@linux.ibm.com \
--cc=jernej.skrabec@gmail.com \
--cc=jmaloy@redhat.com \
--cc=josef@toxicpanda.com \
--cc=kadlec@netfilter.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-um@lists.infradead.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@roeck-us.net \
--cc=lorenzo.stoakes@oracle.com \
--cc=luc.vanoostenryck@gmail.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=malattia@linux.it \
--cc=martin.petersen@oracle.com \
--cc=maz@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mgross@linux.intel.com \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=mripard@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=pablo@netfilter.org \
--cc=peterz@infradead.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=quic_akhilpo@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=rric@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=sakari.ailus@linux.intel.com \
--cc=sashal@kernel.org \
--cc=sean@poorly.run \
--cc=senozhatsky@chromium.org \
--cc=shuah@kernel.org \
--cc=snitzer@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=tzimmermann@suse.de \
--cc=wens@csie.org \
--cc=willy@infradead.org \
--cc=x86@kernel.org \
--cc=ying.xue@windriver.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).