All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: Richard Palethorpe <rpalethorpe@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v5 3/6] Refactor mqns_03 using new LTP API
Date: Fri, 3 Mar 2023 10:25:26 +0100	[thread overview]
Message-ID: <20230303092526.GD4255@pevik> (raw)
In-Reply-To: <20230301152818.4427-4-andrea.cervesato@suse.com>

Hi Andrea,

...
> +++ b/runtest/containers
> @@ -22,7 +22,8 @@ mqns_02 mqns_02
>  mqns_02_clone mqns_02 -m clone
>  mqns_02_unshare mqns_02 -m unshare
>  mqns_03 mqns_03
> -mqns_03_clone mqns_03 -clone
> +mqns_03_clone mqns_03 -m clone
> +mqns_03_unshare mqns_03 -m unshare
Interesting, it was not run with unshare. +1 for adding it.

>  mqns_04 mqns_04
>  mqns_04_clone mqns_04 -clone

> diff --git a/testcases/kernel/containers/mqns/mqns_03.c b/testcases/kernel/containers/mqns/mqns_03.c
...
> +/*\
> + * [Description]
> + *
> + * Test mqueuefs from an isolated/forked process namespace.
Again, I'd mention supported modes here.
> + *
> + * [Algorithm]
> + *
> + * - create /MQ1
> + * - mount mqueue inside the temporary folder
> + * - check for /MQ1 existance
> + * - create /MQ2 inside the temporary folder
> + * - umount
> + * - mount mqueue inside the temporary folder
> + * - check /MQ1 existance
> + * - check /MQ2 existance
> + * - umount
> + */
>  #define _GNU_SOURCE
I wonder why _GNU_SOURCE was used here and in mqns_04.c. I don't see anything
in man mq_open(3), both tests are working without it.

...
> +static void cleanup(void)
> +{
mqns_04.c checks here:
	if (!devdir)
		return;

Although it's unlikely that SAFE_ASPRINTF(&devdir, "%s/mqueue", tmpdir); in
setup() would fail, I'd add it also here.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2023-03-03  8:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 15:28 [LTP] [PATCH v5 0/6] Refactor mqns testing suite Andrea Cervesato via ltp
2023-03-01 15:28 ` [LTP] [PATCH v5 1/6] Refactor mqns_01 using new LTP API Andrea Cervesato via ltp
2023-03-01 15:28 ` [LTP] [PATCH v5 2/6] Refactor mqns_02 " Andrea Cervesato via ltp
2023-03-01 15:28 ` [LTP] [PATCH v5 3/6] Refactor mqns_03 " Andrea Cervesato via ltp
2023-03-03  9:25   ` Petr Vorel [this message]
2023-03-03  8:46     ` Andrea Cervesato via ltp
2023-03-03 10:22       ` Petr Vorel
2023-03-01 15:28 ` [LTP] [PATCH v5 4/6] Refactor mqns_04 " Andrea Cervesato via ltp
2023-03-03  9:16   ` Petr Vorel
2023-03-03  8:45     ` Andrea Cervesato via ltp
2023-03-01 15:28 ` [LTP] [PATCH v5 5/6] Remove deprecated header files from mqns suite Andrea Cervesato via ltp
2023-03-01 15:28 ` [LTP] [PATCH v5 6/6] Remove libclone dependency " Andrea Cervesato via ltp

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=20230303092526.GD4255@pevik \
    --to=pvorel@suse.cz \
    --cc=andrea.cervesato@suse.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.