From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it, Paulson Raja L <lpaulsonraja@gmail.com>
Subject: Re: [LTP] [PATCH] Added test for mmap() with MAP_SHARED_VALIDATE.
Date: Tue, 28 Mar 2023 10:17:10 +0200 [thread overview]
Message-ID: <20230328081710.GB743322@pevik> (raw)
In-Reply-To: <CAEemH2e69a5DOq9eqJVau8YCENZchm8miOH3upQY_Pi6SUFyng@mail.gmail.com>
Hi Li,
> Hi Paulson, Petr,
> Paulson Raja L <lpaulsonraja@gmail.com> wrote:
> > Hi Petr Vorel,
> > Thanks for the comments, I have just started contributing to LTP, and
> > this is my first patch. I agree to merge it as is.
> Good to see a new case for MAP_SHARED_VALIDATE.
> As this is the first test to cover the new flags argument, so I'm
> wondering can we add the functional verification to check if
> this works correctly for mapping a valid shared memory which
> equal to the behavior of MAP_SHARED?
> (or do this in a separate patch)
+1
> But anyway, I'd suggest you send a patch V2 for achieving all
> requested changes.
Li, if you don't mind, I'll merge "v2" I prepared [1] (part of
paulson/mmap.fixes branch in my fork). Can I add your Reviewed-by tag? As the
work is already done, I'd prefer to postpone the work you propose to separate
patch after.
Kind regards,
Petr
[1] https://github.com/pevik/ltp/blob/36ebc4d8900ea8438dc7839f03b7921f0ed9243a/testcases/kernel/syscalls/mmap/mmap20.c
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-03-28 8:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 12:13 [LTP] [PATCH] Added test for mmap() with MAP_SHARED_VALIDATE paulson
2023-03-24 10:33 ` Petr Vorel
2023-03-25 4:01 ` Paulson Raja L
2023-03-27 10:21 ` Petr Vorel
2023-03-28 3:14 ` Li Wang
2023-03-28 8:17 ` Petr Vorel [this message]
2023-03-28 8:30 ` Li Wang
2023-03-28 10:39 ` Petr Vorel
2023-04-04 11:07 ` Petr Vorel
2023-04-04 11:15 ` Petr Vorel
2023-03-27 10:51 ` Petr Vorel
2023-03-28 3:39 ` Li Wang
2023-03-28 8:11 ` Petr Vorel
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=20230328081710.GB743322@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--cc=lpaulsonraja@gmail.com \
--cc=ltp@lists.linux.it \
/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