From: Jeff Xu <jeffxu@chromium.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: akpm@linux-foundation.org, vbabka@suse.cz,
Liam.Howlett@oracle.com, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org, linux-mm@kvack.org,
jorgelo@chromium.org, keescook@chromium.org,
pedro.falcato@gmail.com, rdunlap@infradead.org
Subject: Re: [PATCH v2 1/1] mseal: remove can_do_mseal()
Date: Fri, 6 Dec 2024 12:08:02 -0800 [thread overview]
Message-ID: <CABi2SkV2gSx+5p1uS-YZnD90HzV8ZAFkpbsqSUL5usU+EW8HwA@mail.gmail.com> (raw)
In-Reply-To: <607a69bb-9b6f-4d0e-83aa-1ec6903c34a5@lucifer.local>
On Fri, Dec 6, 2024 at 11:57 AM Lorenzo Stoakes
<lorenzo.stoakes@oracle.com> wrote:
>
> On Fri, Dec 06, 2024 at 07:48:39PM +0000, jeffxu@chromium.org wrote:
> > From: Jeff Xu <jeffxu@chromium.org>
> >
> > No code logic change.
> >
> > can_do_mseal() is called exclusively by mseal.c, and mseal.c is compiled
> > only when CONFIG_64BIT flag is set in makefile. Therefore, it is
> > unnecessary to have 32 bit stub function in the header file, remove
> > this function and merge the logic into do_mseal().
> >
> > Link: https://lkml.kernel.org/r/20241206013934.2782793-1-jeffxu@google.com
Please remove the link field here when applying.
(I pull the mm-unstable and apply my change on top of the existing commit.)
> > Signed-off-by: Jeff Xu <jeffxu@chromium.org>
>
> LGTM,
>
> Reviewed-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>
> > Cc: Jorge Lucangeli Obes <jorgelo@chromium.org>
> > Cc: Kees Cook <keescook@chromium.org>
> > Cc: Liam R. Howlett <Liam.Howlett@Oracle.com>
> > Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> > Cc: Pedro Falcato <pedro.falcato@gmail.com>
> > Cc: Randy Dunlap <rdunlap@infradead.org>
> > Cc: Vlastimil Babka <vbabka@suse.cz>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>
> Not sure you should be submitting a S-o-b for Andrew :P I'm thinking this
> is a copy/paste mistake.
>
I realized where this is coming from after seeing this response.
Thanks for pointing it out
> > ---
> > mm/internal.h | 16 ----------------
> > mm/mseal.c | 6 +++---
> > 2 files changed, 3 insertions(+), 19 deletions(-)
> >
> > diff --git a/mm/internal.h b/mm/internal.h
> > index 74dc1c48fa31..5e4ef5ce9c0a 100644
> > --- a/mm/internal.h
> > +++ b/mm/internal.h
> > @@ -1457,22 +1457,6 @@ void __meminit __init_single_page(struct page *page, unsigned long pfn,
> > unsigned long shrink_slab(gfp_t gfp_mask, int nid, struct mem_cgroup *memcg,
> > int priority);
> >
> > -#ifdef CONFIG_64BIT
> > -static inline int can_do_mseal(unsigned long flags)
> > -{
> > - if (flags)
> > - return -EINVAL;
> > -
> > - return 0;
> > -}
> > -
> > -#else
> > -static inline int can_do_mseal(unsigned long flags)
> > -{
> > - return -EPERM;
> > -}
> > -#endif
> > -
> > #ifdef CONFIG_SHRINKER_DEBUG
> > static inline __printf(2, 0) int shrinker_debugfs_name_alloc(
> > struct shrinker *shrinker, const char *fmt, va_list ap)
> > diff --git a/mm/mseal.c b/mm/mseal.c
> > index 81d6e980e8a9..c27197ac04e8 100644
> > --- a/mm/mseal.c
> > +++ b/mm/mseal.c
> > @@ -217,9 +217,9 @@ int do_mseal(unsigned long start, size_t len_in, unsigned long flags)
> > unsigned long end;
> > struct mm_struct *mm = current->mm;
> >
> > - ret = can_do_mseal(flags);
> > - if (ret)
> > - return ret;
> > + /* Verify flags not set. */
> > + if (flags)
> > + return -EINVAL;
> >
> > start = untagged_addr(start);
> > if (!PAGE_ALIGNED(start))
> > --
> > 2.47.0.338.g60cca15819-goog
> >
prev parent reply other threads:[~2024-12-06 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 19:48 [PATCH v2 0/1] remove can_do_mseal jeffxu
2024-12-06 19:48 ` [PATCH v2 1/1] mseal: remove can_do_mseal() jeffxu
2024-12-06 19:56 ` Lorenzo Stoakes
2024-12-06 20:08 ` Jeff Xu [this message]
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=CABi2SkV2gSx+5p1uS-YZnD90HzV8ZAFkpbsqSUL5usU+EW8HwA@mail.gmail.com \
--to=jeffxu@chromium.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jorgelo@chromium.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=pedro.falcato@gmail.com \
--cc=rdunlap@infradead.org \
--cc=vbabka@suse.cz \
/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