public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] mm/mseal: use min/max in mseal_apply
@ 2026-05-03 11:59 Thorsten Blum
  2026-05-03 20:58 ` Pedro Falcato
  0 siblings, 1 reply; 3+ messages in thread
From: Thorsten Blum @ 2026-05-03 11:59 UTC (permalink / raw)
  To: Andrew Morton, Liam R. Howlett, Lorenzo Stoakes, Vlastimil Babka,
	Jann Horn, Pedro Falcato
  Cc: Thorsten Blum, linux-mm, linux-kernel

Use the type-checked min()/max() macros instead of MIN()/MAX(), which
are supposed to be used "for obvious constants only".

Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
---
 mm/mseal.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/mm/mseal.c b/mm/mseal.c
index e2093ae3d25c..9781647483d1 100644
--- a/mm/mseal.c
+++ b/mm/mseal.c
@@ -8,6 +8,7 @@
  */
 
 #include <linux/mempolicy.h>
+#include <linux/minmax.h>
 #include <linux/mman.h>
 #include <linux/mm.h>
 #include <linux/mm_inline.h>
@@ -65,8 +66,8 @@ static int mseal_apply(struct mm_struct *mm,
 		prev = vma;
 
 	for_each_vma_range(vmi, vma, end) {
-		const unsigned long curr_start = MAX(vma->vm_start, start);
-		const unsigned long curr_end = MIN(vma->vm_end, end);
+		const unsigned long curr_start = max(vma->vm_start, start);
+		const unsigned long curr_end = min(vma->vm_end, end);
 
 		if (!vma_test(vma, VMA_SEALED_BIT)) {
 			vma_flags_t vma_flags = vma->flags;

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] mm/mseal: use min/max in mseal_apply
  2026-05-03 11:59 [PATCH] mm/mseal: use min/max in mseal_apply Thorsten Blum
@ 2026-05-03 20:58 ` Pedro Falcato
  2026-05-04 12:36   ` David Laight
  0 siblings, 1 reply; 3+ messages in thread
From: Pedro Falcato @ 2026-05-03 20:58 UTC (permalink / raw)
  To: Thorsten Blum
  Cc: Andrew Morton, Liam R. Howlett, Lorenzo Stoakes, Vlastimil Babka,
	Jann Horn, linux-mm, linux-kernel

On Sun, May 03, 2026 at 01:59:16PM +0200, Thorsten Blum wrote:
> Use the type-checked min()/max() macros instead of MIN()/MAX(), which
> are supposed to be used "for obvious constants only".

Gotta love these macros... FYI this isn't the only wrong usage in the kernel.

> 
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>

Reviewed-by: Pedro Falcato <pfalcato@suse.de>

-- 
Pedro

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] mm/mseal: use min/max in mseal_apply
  2026-05-03 20:58 ` Pedro Falcato
@ 2026-05-04 12:36   ` David Laight
  0 siblings, 0 replies; 3+ messages in thread
From: David Laight @ 2026-05-04 12:36 UTC (permalink / raw)
  To: Pedro Falcato
  Cc: Thorsten Blum, Andrew Morton, Liam R. Howlett, Lorenzo Stoakes,
	Vlastimil Babka, Jann Horn, linux-mm, linux-kernel

On Sun, 3 May 2026 21:58:57 +0100
Pedro Falcato <pfalcato@suse.de> wrote:

> On Sun, May 03, 2026 at 01:59:16PM +0200, Thorsten Blum wrote:
> > Use the type-checked min()/max() macros instead of MIN()/MAX(), which
> > are supposed to be used "for obvious constants only".  
> 
> Gotta love these macros... FYI this isn't the only wrong usage in the kernel.

I failed to persuade Linus to include a test for __builtin_constant_p((a)|(b)) :-)

-- David

> 
> > 
> > Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>  
> 
> Reviewed-by: Pedro Falcato <pfalcato@suse.de>
> 


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-05-04 12:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-03 11:59 [PATCH] mm/mseal: use min/max in mseal_apply Thorsten Blum
2026-05-03 20:58 ` Pedro Falcato
2026-05-04 12:36   ` David Laight

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox