linux-kernel - Re: [PATCH v3 1/7] mm: Move can_modify

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKbZUD0XGESusp8FmGsR_OAiT_1X8gKFURpMiNN63xyaM+Q-6A@mail.gmail.com>
Date: Mon, 19 Aug 2024 22:00:08 +0100
From: Pedro Falcato <pedro.falcato@...il.com>
To: "Liam R. Howlett" <Liam.Howlett@...cle.com>, Pedro Falcato <pedro.falcato@...il.com>, 
	Andrew Morton <akpm@...ux-foundation.org>, Vlastimil Babka <vbabka@...e.cz>, 
	Lorenzo Stoakes <lorenzo.stoakes@...cle.com>, Shuah Khan <shuah@...nel.org>, linux-mm@...ck.org, 
	linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org, 
	jeffxu@...omium.org, oliver.sang@...el.com, torvalds@...ux-foundation.org, 
	Michael Ellerman <mpe@...erman.id.au>, Kees Cook <kees@...nel.org>
Subject: Re: [PATCH v3 1/7] mm: Move can_modify_vma to mm/vma.h

On Mon, Aug 19, 2024 at 9:15 PM Liam R. Howlett <Liam.Howlett@...cle.com> wrote:
>
> * Pedro Falcato <pedro.falcato@...il.com> [240816 20:18]:
> > Move can_modify_vma to vma.h so it can be inlined properly (with
> > the intent to remove can_modify_mm callsites).
> >
> > Signed-off-by: Pedro Falcato <pedro.falcato@...il.com>
> > ---
> >  mm/mseal.c | 17 -----------------
> >  mm/vma.h   | 28 ++++++++++++++++++++++++++++
> >  2 files changed, 28 insertions(+), 17 deletions(-)
> >
> > diff --git a/mm/mseal.c b/mm/mseal.c
> > index 15bba28acc00..2170e2139ca0 100644
> > --- a/mm/mseal.c
> > +++ b/mm/mseal.c
> > @@ -16,28 +16,11 @@
> >  #include <linux/sched.h>
> >  #include "internal.h"
> >
> > -static inline bool vma_is_sealed(struct vm_area_struct *vma)
> > -{
> > -     return (vma->vm_flags & VM_SEALED);
> > -}
> > -
> >  static inline void set_vma_sealed(struct vm_area_struct *vma)
> >  {
> >       vm_flags_set(vma, VM_SEALED);
> >  }
> >
> > -/*
> > - * check if a vma is sealed for modification.
> > - * return true, if modification is allowed.
> > - */
> > -static bool can_modify_vma(struct vm_area_struct *vma)
> > -{
> > -     if (unlikely(vma_is_sealed(vma)))
> > -             return false;
> > -
> > -     return true;
> > -}
> > -
> >  static bool is_madv_discard(int behavior)
> >  {
> >       switch (behavior) {
> > diff --git a/mm/vma.h b/mm/vma.h
> > index 6efdf1768a0a..e979015cc7fc 100644
> > --- a/mm/vma.h
> > +++ b/mm/vma.h
> > @@ -361,4 +361,32 @@ struct vm_area_struct *vma_iter_prev_range(struct vma_iterator *vmi)
> >       return mas_prev_range(&vmi->mas, 0);
> >  }
> >
> > +#ifdef CONFIG_64BIT
> > +
> > +static inline bool vma_is_sealed(struct vm_area_struct *vma)
> > +{
> > +     return (vma->vm_flags & VM_SEALED);
> > +}
>
> If you respin, I'd support dropping this entirely as it seems
> unnecessary.

ACK, I'll fold this into the next patch if the need for v4 arises.

> Either way,
> Reviewed-by: Liam R. Howlett <Liam.Howlett@...cle.com>

Thank you for the speedy review(s)!

-- 
Pedro