linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Jeff Xu <jeffxu@chromium.org>
Cc: Jeff Xu <jeffxu@google.com>,
	akpm@linux-foundation.org, willy@infradead.org,
	torvalds@linux-foundation.org, pedro.falcato@gmail.com,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-mm@kvack.org, linux-hardening@vger.kernel.org,
	lorenzo.stoakes@oracle.com, mpe@ellerman.id.au,
	oliver.sang@intel.com, vbabka@suse.cz, keescook@chromium.org
Subject: Re: [PATCH v1 0/2] mremap refactor: check src address for vma boundaries first.
Date: Thu, 15 Aug 2024 16:40:35 -0400	[thread overview]
Message-ID: <77w7ubt4f7hmpc5grmcmzey7kuav634zzgmk7amwbx47tols3g@ptjbrd2w4ay3> (raw)
In-Reply-To: <CABi2SkU84jZFa8qGPQen9g16zQ9E-Z9VOuUE+HjNDSMCPoRA1g@mail.gmail.com>

* Jeff Xu <jeffxu@chromium.org> [240815 16:23]:
> On Thu, Aug 15, 2024 at 1:14 PM Liam R. Howlett <Liam.Howlett@oracle.com> wrote:
> >
> > * Jeff Xu <jeffxu@google.com> [240815 13:23]:
> > > On Thu, Aug 15, 2024 at 9:50 AM Liam R. Howlett <Liam.Howlett@oracle.com> wrote:
> > > >
> > > > * Jeff Xu <jeffxu@chromium.org> [240814 23:46]:
> > > > > On Wed, Aug 14, 2024 at 12:55 PM Liam R. Howlett
> > > > > <Liam.Howlett@oracle.com> wrote:
> > > > > > The majority of the comments to V2 are mine, you only told us that
> > > > > > splitting a sealed vma is wrong (after I asked you directly to answer)
> > > > > > and then you made a comment about testing of the patch set. Besides the
> > > > > > direct responses to me, your comment was "wait for me to test".
> > > > > >
> > > > > Please share this link for  " Besides the direct responses to me, your
> > > > > comment was "wait for me to test".
> > > > > Or  pop up that email by responding to it, to remind me.  Thanks.
> > > >
> > > > [1].
> > >
> > > That is responding to Andrew, to indicate V2 patch has dependency on
> > > arch_munmap in PPC. And I will review/test the code, I will respond to
> > > Andrew directly.
> > >
> > > PS Your statement above is entirely false, and out of context.
> > >
> > > " You only told us that splitting a sealed vma is wrong (after I asked
> > > you directly to answer) and then you made a comment about testing of
> > > the patch set. Besides the direct responses to me, your comment was
> > > "wait for me to test".
> >
> > [1] has your "wait for me to test" to hold up a patch set, [2] has you
> > answering my direct question to you and making the untested comment to
> > someone else.
> >
> This is the last time that I'm trying to clarify this.
> [1] is my response to Andrew and Pedro.

That doesn't change what you said, or what you are doing.

> [2] is my comments about V2 lack of test , i.e. no selftest change, no
> extra tests added.

But they pass the tests that exist.

Maybe you should take a step back, and look at both solutions.  There is
a competing set of patches that fixes the same problem in a similar way
that was sent out before these patches, and those patches address the
entire problem with the mseal() approach.

Instead of helping make the complete solution work as you think it
should, you are making the design problem worse and can't seem to verify
your patches actually fix the regression.

Liam


  reply	other threads:[~2024-08-15 20:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14  7:14 jeffxu
2024-08-14  7:14 ` [PATCH v1 1/2] mseal:selftest mremap across VMA boundaries jeffxu
2024-08-14  7:14 ` [PATCH v1 2/2] mseal: refactor mremap to remove can_modify_mm jeffxu
2024-08-14 14:39 ` [PATCH v1 0/2] mremap refactor: check src address for vma boundaries first Liam R. Howlett
2024-08-14 16:57   ` Jeff Xu
2024-08-14 19:55     ` Liam R. Howlett
2024-08-15  3:45       ` Jeff Xu
2024-08-15 16:49         ` Liam R. Howlett
2024-08-15 17:22           ` Jeff Xu
2024-08-15 20:14             ` Liam R. Howlett
2024-08-15 20:23               ` Jeff Xu
2024-08-15 20:40                 ` Liam R. Howlett [this message]
2024-08-15 18:16 ` Jeff Xu
2024-08-15 20:19   ` Jeff Xu
2024-08-16  2:39     ` Oliver Sang
2024-08-16  2:58       ` Jeff Xu
2024-08-18  9:28         ` Oliver Sang
2024-08-19  1:38           ` Oliver Sang
2024-08-19  6:35             ` Oliver Sang
2024-08-21  6:19               ` Oliver Sang
2024-08-21 15:21                 ` Jeff Xu

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=77w7ubt4f7hmpc5grmcmzey7kuav634zzgmk7amwbx47tols3g@ptjbrd2w4ay3 \
    --to=liam.howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=jeffxu@chromium.org \
    --cc=jeffxu@google.com \
    --cc=keescook@chromium.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mpe@ellerman.id.au \
    --cc=oliver.sang@intel.com \
    --cc=pedro.falcato@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.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