linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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,
	Jeff Xu <jeffxu@google.com>
Subject: Re: [PATCH] mseal: remove can_do_mseal
Date: Fri, 6 Dec 2024 11:53:13 -0800	[thread overview]
Message-ID: <CABi2SkUeALssNiEwcUHNQ7AUWY2UvScJmw4LJWo5+fV94_42Jg@mail.gmail.com> (raw)
In-Reply-To: <456abc34-9071-46f0-8c70-62377484dbf0@lucifer.local>

On Fri, Dec 6, 2024 at 11:39 AM Lorenzo Stoakes
<lorenzo.stoakes@oracle.com> wrote:
>
> On Fri, Dec 06, 2024 at 07:33:09PM +0000, jeffxu@chromium.org wrote:
> > From: Jeff Xu <jeffxu@google.com>
> >
> > Hi Andrew,
> >
> > Is that possible to squash this change on top of
> > "mseal: move can_do_mseal to mseal.c" on the mm-unstable ?
> >
> > This is the first time I m doing this, because I saw dev did this before,
> > and saying this is the prefered approach.
> >
> > I could also send v2 which is what I usually do.
> >
> > Thanks
> > -Jeff
> >
> > Signed-off-by: Jeff Xu <jeffxu@chromium.org>
>
> Hi Jeff,
>
> Fix-patches and the like are usually for stuff that's been taken and this, I
> don't believe has (I might be wrong actually).
>
sure.

> But anyway, as a reviewer it's easier for me to deal with a v2 in this case, I
> am not going to give tags to the original version of this and want to make it
> explicit I am only giving them to the corrected version.
>
> So from my perspective could you do a favour and send as a v2 as it makes my
> life easier anyway? :)
>
sure.

> Thanks, Lorenzo
>
> > ---
> >  mm/mseal.c | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/mm/mseal.c b/mm/mseal.c
> > index e167220a0bf0..08e6f328d9c7 100644
> > --- a/mm/mseal.c
> > +++ b/mm/mseal.c
> > @@ -225,9 +225,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
> >


      reply	other threads:[~2024-12-06 19:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06  1:39 [PATCH v1] mseal: move can_do_mseal to mseal.c jeffxu
2024-12-06  4:25 ` Liam R. Howlett
2024-12-06  9:12   ` Lorenzo Stoakes
2024-12-06 16:17     ` Jeff Xu
2024-12-06 17:04       ` Lorenzo Stoakes
2024-12-11  2:38         ` Jeff Xu
2024-12-11  8:35           ` Lorenzo Stoakes
2024-12-06 16:11   ` Jeff Xu
2024-12-06 19:33     ` [PATCH] mseal: remove can_do_mseal jeffxu
2024-12-06 19:37       ` Jeff Xu
2024-12-06 19:39       ` Lorenzo Stoakes
2024-12-06 19:53         ` 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=CABi2SkUeALssNiEwcUHNQ7AUWY2UvScJmw4LJWo5+fV94_42Jg@mail.gmail.com \
    --to=jeffxu@chromium.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=jeffxu@google.com \
    --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