From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Jeff Xu <jeffxu@chromium.org>
Cc: akpm@linux-foundation.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, linux-hardening@vger.kernel.org,
pedro.falcato@gmail.com, rientjes@google.com,
keescook@chromium.org,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH v1 2/2] selftests/mm: mseal_test add more tests
Date: Thu, 29 Aug 2024 16:14:41 +0100 [thread overview]
Message-ID: <097a3458-0126-48e3-ba0d-d7dc7b9069d2@lucifer.local> (raw)
In-Reply-To: <CABi2SkW9qEOx1FAcWeBLx_EA8LT2V_U6OS1GmEP433oA6t35pw@mail.gmail.com>
On Thu, Aug 29, 2024 at 07:45:56AM GMT, Jeff Xu wrote:
> HI Andrew
>
> On Wed, Aug 28, 2024 at 3:55 PM <jeffxu@chromium.org> wrote:
> >
> > From: Jeff Xu <jeffxu@chromium.org>
> >
> > Add more testcases and increase test coverage, e.g. add
> > get_vma_size to check VMA size and prot bits.
This commit message is ridiculously short for such a massive change, even for
test code.
> >
>
> Could you please pull the self-test part of this patch series to mm-unstable ?
> It will help to prevent regression.
No, please don't.
This needs review.
These tests establish a precedent as to how mseal should behave, this is
something that needs community review, not to just be taken.
There's already been a great deal of confusion/contentious discussion
around mseal() and its implementation.
Pushing in ~800 lines of test code asserting how mseal() should behave
without review isn't helping things.
Also, this is a really unusual way to send a series - why is this a 2/2 in
reply to the 1/2 and no cover letter? Why is this change totally unrelated
to the other patch?
Can you send this as a separate patch, preferably as an RFC so we can
ensure that we all agree on how mseal() should behave?
Sorry to be contentious here, but I think we need to find a more
constructive, collaborative way forward with mseal() and to act with a
little more caution, given the problems that the original series has caused
I'd think this is in the best interests of all.
Thanks for understanding!
>
> The first part ([PATCH v1 1/2] mseal: fix mmap(FIXED) error code) can
> be ignored as Liam proposed to fix it differently.
>
> Thanks
> -Jeff
>
> -Jeff
>
> > Signed-off-by: Jeff Xu <jeffxu@chromium.org>
> > ---
> > tools/testing/selftests/mm/mseal_test.c | 826 ++++++++++++++++++++++--
> > 1 file changed, 759 insertions(+), 67 deletions(-)
> >
> > diff --git a/tools/testing/selftests/mm/mseal_test.c b/tools/testing/selftests/mm/mseal_test.c
> > index e7991e5fdcf3..4b3f883aae17 100644
> > --- a/tools/testing/selftests/mm/mseal_test.c
> > +++ b/tools/testing/selftests/mm/mseal_test.c
next prev parent reply other threads:[~2024-08-29 15:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 22:55 [PATCH v1 1/2] mseal: fix mmap(FIXED) error code jeffxu
2024-08-28 22:55 ` [PATCH v1 2/2] selftests/mm: mseal_test add more tests jeffxu
2024-08-29 14:45 ` Jeff Xu
2024-08-29 15:14 ` Lorenzo Stoakes [this message]
2024-08-29 15:30 ` Jeff Xu
2024-08-29 15:44 ` Lorenzo Stoakes
2024-08-29 19:54 ` Jeff Xu
2024-08-29 19:58 ` Matthew Wilcox
2024-08-29 21:34 ` Jeff Xu
2024-08-29 16:16 ` Mark Brown
2024-08-29 16:32 ` Lorenzo Stoakes
2024-08-29 19:40 ` Jeff Xu
2024-08-28 23:38 ` [PATCH v1 1/2] mseal: fix mmap(FIXED) error code Pedro Falcato
2024-08-29 14:03 ` Liam R. Howlett
2024-08-29 14:36 ` Jeff Xu
2024-08-29 14:32 ` Jeff Xu
2024-08-29 12:09 ` Lorenzo Stoakes
2024-08-29 14:34 ` Jeff Xu
2024-08-31 1:15 ` Andrew Morton
2024-08-31 10:14 ` Lorenzo Stoakes
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=097a3458-0126-48e3-ba0d-d7dc7b9069d2@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jeffxu@chromium.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pedro.falcato@gmail.com \
--cc=rientjes@google.com \
--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