From: Oliver Sang <oliver.sang@intel.com>
To: Jeff Xu <jeffxu@google.com>
Cc: Jeff Xu <jeffxu@chromium.org>, <akpm@linux-foundation.org>,
<willy@infradead.org>, <torvalds@linux-foundation.org>,
<Liam.Howlett@oracle.com>, <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>,
<vbabka@suse.cz>, <keescook@chromium.org>,
<oliver.sang@intel.com>
Subject: Re: [PATCH v1 0/2] mremap refactor: check src address for vma boundaries first.
Date: Mon, 19 Aug 2024 09:38:19 +0800 [thread overview]
Message-ID: <ZsKiC+MSWbAOxxDA@xsang-OptiPlex-9020> (raw)
In-Reply-To: <ZsG+yfTDCQSd1Lh7@xsang-OptiPlex-9020>
hi, Jeff,
On Sun, Aug 18, 2024 at 05:28:41PM +0800, Oliver Sang wrote:
> hi, Jeff,
>
> On Thu, Aug 15, 2024 at 07:58:57PM -0700, Jeff Xu wrote:
> > Hi Oliver
>
> [...]
>
> > > could you exlictly point to two commit-id?
> > sure
> >
> > this patch
> > 8be7258a: mseal: add mseal syscall
> > ff388fe5c: mseal: wire up mseal syscall
>
> I failed to apply this patch set to "8be7258a: mseal: add mseal syscall"
look your patch set again
[PATCH v1 1/2] mseal:selftest mremap across VMA boundaries
just for kselftests
and I can apply
[PATCH v1 2/2] mseal: refactor mremap to remove can_modify_mm
upon "8be7258a: mseal: add mseal syscall" cleanly
so I will start test for this [PATCH v1 2/2]
BTW, I will firstly use our default setting - "60s testtime; reboot between each
run; run 10 times", since we've already have the data for 8be7258a and ff388fe5c
then we could give you an update kind of quickly.
as some private mail discussed, you want some special run method, could you
elaborate them here? thanks
>
> to avoid the impact of other changes, better to apply the patch upon 8be7258a
> directly.
>
> if you prefer other base for this patch, please let us know. then we will
> supply the results for 4 commits in fact:
>
> this patch
> the base of this patch
> 8be7258a: mseal: add mseal syscall
> ff388fe5c: mseal: wire up mseal syscall
>
> >
> > > >
> > > > Thank you for your time and assistance in helping me on understanding
> > > > this issue.
> > >
> > > due to resource constraint, please expect that we need several days to finish
> > > this test request.
> > No problem.
> >
> > Thanks for your help!
> > -Jeff
> >
> > > >
> > > > Best regards,
> > > > -Jeff
> > > >
> > > > > -Jeff
> > > > >
> > > > > > [1] https://lore.kernel.org/lkml/202408041602.caa0372-oliver.sang@intel.com/
> > > > > > [2] https://github.com/peaktocreek/mmperf/blob/main/run_stress_ng.c
> > > > > >
> > > > > >
> > > > > > Jeff Xu (2):
> > > > > > mseal:selftest mremap across VMA boundaries.
> > > > > > mseal: refactor mremap to remove can_modify_mm
> > > > > >
> > > > > > mm/internal.h | 24 ++
> > > > > > mm/mremap.c | 77 +++----
> > > > > > mm/mseal.c | 17 --
> > > > > > tools/testing/selftests/mm/mseal_test.c | 293 +++++++++++++++++++++++-
> > > > > > 4 files changed, 353 insertions(+), 58 deletions(-)
> > > > > >
> > > > > > --
> > > > > > 2.46.0.76.ge559c4bf1a-goog
> > > > > >
next prev parent reply other threads:[~2024-08-19 1:38 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
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 [this message]
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=ZsKiC+MSWbAOxxDA@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=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=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