From: Colin Ian King <colin.king@canonical.com>
To: Piyush Goyal <piyushgoyaliit@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] stress-shm-sysv: exercise shmat with invalid flags
Date: Tue, 22 Sep 2020 09:16:49 +0100 [thread overview]
Message-ID: <c867a2f8-5046-ce14-e36a-3d48780c317a@canonical.com> (raw)
In-Reply-To: <20200922072730.68911-1-piyushgoyaliit@gmail.com>
I believe these patches should have gone directly to me and not various
other folk.
Colin
On 22/09/2020 08:27, Piyush Goyal wrote:
> Exercise shmat syscall with invalid flags resulting in more kernel
> coverage.
>
> Signed-off-by: Piyush Goyal <piyushgoyaliit@gmail.com>
> ---
> stress-shm-sysv.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/stress-shm-sysv.c b/stress-shm-sysv.c
> index aa03d718..5a3e0cc1 100644
> --- a/stress-shm-sysv.c
> +++ b/stress-shm-sysv.c
> @@ -128,6 +128,19 @@ static int stress_shm_sysv_check(
> return 0;
> }
>
> +/*
> + * exercise_shmat()
> + * exercise shmat syscall with all possible values of arguments
> + */
> +static void exercise_shmat(int shm_id)
> +{
> + void *addr;
> +
> + /* Exercise shmat syscall with invalid flags */
> + addr = shmat(shm_id, NULL, ~0);
> + (void)addr;
> +}
> +
> #if defined(__linux__)
> /*
> * stress_shm_get_procinfo()
> @@ -337,6 +350,7 @@ static int stress_shm_sysv_child(
> goto reap;
> }
>
> + exercise_shmat(shm_id);
> addr = shmat(shm_id, NULL, 0);
> if (addr == (char *) -1) {
> ok = false;
>
prev parent reply other threads:[~2020-09-22 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 7:27 Piyush Goyal
2020-09-22 7:27 ` [PATCH 2/3] stress-shm-sysv: exercise shmat with all possible flags Piyush Goyal
2020-09-22 7:27 ` [PATCH 3/3] stress-shmsysv: exercise shmat with SHM_REMAP flag on NULL address Piyush Goyal
2020-09-22 8:16 ` Colin Ian King [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=c867a2f8-5046-ce14-e36a-3d48780c317a@canonical.com \
--to=colin.king@canonical.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=piyushgoyaliit@gmail.com \
/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
all inboxes | Powered by JetHome®