From: Shuah Khan <skhan@linuxfoundation.org>
To: Ivan Orlov <ivan.orlov0322@gmail.com>,
shuah@kernel.org, colin.i.king@gmail.com
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
himadrispandya@gmail.com, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] selftests: prctl: Add new prctl test for PR_SET_VMA action
Date: Tue, 28 Mar 2023 10:55:19 -0600 [thread overview]
Message-ID: <ad8b13fe-b732-e4d9-874c-949701bf47a9@linuxfoundation.org> (raw)
In-Reply-To: <20230325205903.5550-1-ivan.orlov0322@gmail.com>
On 3/25/23 14:59, Ivan Orlov wrote:
> This patch will add the new test, which covers the prctl call with
> PR_SET_VMA command. The test tries to give a name to the anonymous
> VMA within the process memory map, and then checks the result of
> the operation by parsing 'maps' virtual file.
>
> Additionally, the test tries to call the prctl PR_SET_VMA command
> with invalid arguments, and checks the error codes for correctness.
>
> At the moment anonymous VMA naming through prctl call functionality
> is not covered with any tests, so I think implementing it makes sense.
>
> In version 2 of this patch I consider the selftest Makefile rule about
> TARGETS entries order - I moved the 'prctl' entry in the Makefile to
> follow the lexicographic order. In version 1 it was placed at the
> end of the list.
>
> Signed-off-by: Ivan Orlov <ivan.orlov0322@gmail.com>
> ---
Thank you. Applied to linux-kselftest next for Linux 6.4-rc1.
thanks,
-- Shuah
prev parent reply other threads:[~2023-03-28 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 20:59 [PATCH v2] selftests: prctl: Add new prctl test for PR_SET_VMA action Ivan Orlov
2023-03-28 16:55 ` Shuah Khan [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=ad8b13fe-b732-e4d9-874c-949701bf47a9@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=colin.i.king@gmail.com \
--cc=himadrispandya@gmail.com \
--cc=ivan.orlov0322@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.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