From: Petr Vorel <pvorel@suse.cz>
To: Yang Xu <xuyang2018.jy@fujitsu.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 3/3] umount03: Simplify test using TST_ macros
Date: Thu, 26 Oct 2023 02:05:39 +0200 [thread overview]
Message-ID: <20231026000539.GB540370@pevik> (raw)
In-Reply-To: <1697100058-2859-3-git-send-email-xuyang2018.jy@fujitsu.com>
Hi Xu,
> Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com>
> ---
> testcases/kernel/syscalls/umount/umount03.c | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
this is not needed:
#include <errno.h>
This is for all 3 patches.
> diff --git a/testcases/kernel/syscalls/umount/umount03.c b/testcases/kernel/syscalls/umount/umount03.c
> index 1cef06fa1..e6bb523b4 100644
> --- a/testcases/kernel/syscalls/umount/umount03.c
> +++ b/testcases/kernel/syscalls/umount/umount03.c
> @@ -1,6 +1,7 @@
> // SPDX-License-Identifier: GPL-2.0-or-later
> /*
> * Copyright (c) Wipro Technologies Ltd, 2002. All Rights Reserved.
> + * Copyright (c) Linux Test Project, 2003-2023
> * Author: Nirmala Devi Dhanasekar <nirmala.devi@wipro.com>
> *
> * Verify that umount(2) returns -1 and sets errno to EPERM if the user
> @@ -20,19 +21,12 @@ static int mount_flag;
> static void verify_umount(void)
> {
> - TEST(umount(MNTPOINT));
> -
> - if (TST_RET != -1) {
> - tst_res(TFAIL, "umount() succeeds unexpectedly");
> - return;
> - }
> + TST_EXP_FAIL(umount(MNTPOINT), EPERM, "umount(%s) Failed", MNTPOINT);
nit: I would prefer just:
TST_EXP_FAIL(umount(MNTPOINT), EPERM);
> if (TST_ERR != EPERM) {
> tst_res(TFAIL | TTERRNO, "umount() should fail with EPERM");
> return;
> }
This should have been removed, it's redundant when TST_EXP_FAIL() is done.
> -
> - tst_res(TPASS | TTERRNO, "umount() fails as expected");
> }
> static void setup(void)
With <errno.h> and if (TST_ERR != EPERM) removed you can add:
Reviewed-by: Petr Vorel <pvorel@suse.cz>
It would be good (as a separate commit) to reword the documentation and convert
it to docparse. Feel free to do it, or please let me know if I should do it.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-10-26 0:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 8:40 [LTP] [PATCH 1/3] umount01: Simplify test using TST_ macros Yang Xu
2023-10-12 8:40 ` [LTP] [PATCH 2/3] umount02: " Yang Xu
2023-10-26 0:12 ` Petr Vorel
2023-10-26 5:40 ` [LTP] 回复: " Yang Xu (Fujitsu)
2023-10-12 8:40 ` [LTP] [PATCH 3/3] umount03: " Yang Xu
2023-10-26 0:05 ` Petr Vorel [this message]
2023-10-26 0:06 ` Petr Vorel
2023-10-26 6:07 ` [LTP] 回复: " Yang Xu (Fujitsu)
2023-10-26 6:05 ` Yang Xu (Fujitsu)
2023-10-20 9:49 ` [LTP] [PATCH 1/3] umount01: " Yang Xu (Fujitsu)
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=20231026000539.GB540370@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=xuyang2018.jy@fujitsu.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.