From: Cyril Hrubis <chrubis@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] msgrcv02: Add negative msgtyp tests
Date: Wed, 13 Oct 2021 12:06:51 +0200 [thread overview]
Message-ID: <YWavuzI2JrJXLDtO@yuki> (raw)
In-Reply-To: <20211012092858.29992-1-rpalethorpe@suse.com>
Hi!
> Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
> Suggested-by: Cyril Hrubis <chrubis@suse.cz>
> ---
> .../kernel/syscalls/ipc/msgrcv/msgrcv02.c | 19 ++++++++++++-------
> 1 file changed, 12 insertions(+), 7 deletions(-)
>
> diff --git a/testcases/kernel/syscalls/ipc/msgrcv/msgrcv02.c b/testcases/kernel/syscalls/ipc/msgrcv/msgrcv02.c
> index cfb7d7446..fba6a5289 100644
> --- a/testcases/kernel/syscalls/ipc/msgrcv/msgrcv02.c
> +++ b/testcases/kernel/syscalls/ipc/msgrcv/msgrcv02.c
> @@ -21,6 +21,8 @@
> * msgflg and no message of the requested type existed on the message queue.
> */
>
> +#define _GNU_SOURCE
> +
> #include <string.h>
> #include <sys/wait.h>
> #include <sys/msg.h>
> @@ -38,7 +40,7 @@ struct passwd *pw;
> static struct buf {
> long type;
> char mtext[MSGSIZE];
> -} rcv_buf, snd_buf = {MSGTYPE, "hello"};
> +} rcv_buf, snd_buf = {2, "hello"};
>
> static struct tcase {
> int *id;
> @@ -49,12 +51,15 @@ static struct tcase {
> int exp_user;
> int exp_err;
> } tcases[] = {
> - {&queue_id, &rcv_buf, 4, 1, 0, 0, E2BIG},
> - {&queue_id, &rcv_buf, MSGSIZE, 1, 0, 1, EACCES},
> - {&queue_id, NULL, MSGSIZE, 1, 0, 0, EFAULT},
> - {&bad_id, &rcv_buf, MSGSIZE, 1, 0, 0, EINVAL},
> - {&queue_id, &rcv_buf, -1, 1, 0, 0, EINVAL},
> - {&queue_id, &rcv_buf, MSGSIZE, 2, IPC_NOWAIT, 0, ENOMSG},
> + {&queue_id, &rcv_buf, MSGSIZE - 1, 2, 0, 0, E2BIG},
> + {&queue_id, &rcv_buf, MSGSIZE, 2, 0, 1, EACCES},
> + {&queue_id, NULL, MSGSIZE, 2, 0, 0, EFAULT},
> + {&bad_id, &rcv_buf, MSGSIZE, 2, 0, 0, EINVAL},
> + {&queue_id, &rcv_buf, -1, 2, 0, 0, EINVAL},
> +
I wouldn't have added this empty line. The rest of the spaces that
aligns the fields looks good to me though, it's easier to read that way.
> + {&queue_id, &rcv_buf, MSGSIZE, 3, IPC_NOWAIT, 0, ENOMSG},
> + {&queue_id, &rcv_buf, MSGSIZE, -1, IPC_NOWAIT, 0, ENOMSG},
> + {&queue_id, &rcv_buf, MSGSIZE, -1, IPC_NOWAIT | MSG_EXCEPT, 0, ENOMSG},
> };
With the empty line removed:
Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-10-13 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 9:28 [LTP] [PATCH] msgrcv02: Add negative msgtyp tests Richard Palethorpe via ltp
2021-10-13 8:24 ` xuyang2018.jy
2021-10-13 10:06 ` Cyril Hrubis [this message]
2021-10-13 11:32 ` Richard Palethorpe
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=YWavuzI2JrJXLDtO@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.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