From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 2/5] swapon03: Cleanup
Date: Tue, 11 Nov 2025 14:04:39 +0100 [thread overview]
Message-ID: <aRM0Z-IlZSLdB5ho@yuki.lan> (raw)
In-Reply-To: <20251106163500.1063704-3-pvorel@suse.cz>
Hi!
> - Remove unused return code in check_and_swapoff() and setup_swap(). The
> purpose was to run cleanup() in the end of the setup() if creating
> swap fails, but return code is always 0. Also cleanup() should be run
> when test exits with tst_brk() anyway.
> - Change return code from TFAIL to TBROK.
> - Add missing brackets.
>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> The same as in v1.
> I can split this if you like.
>
> testcases/kernel/syscalls/swapon/swapon03.c | 23 +++++++--------------
> 1 file changed, 7 insertions(+), 16 deletions(-)
>
> diff --git a/testcases/kernel/syscalls/swapon/swapon03.c b/testcases/kernel/syscalls/swapon/swapon03.c
> index 01a3b6d8ac..d9822c01ef 100644
> --- a/testcases/kernel/syscalls/swapon/swapon03.c
> +++ b/testcases/kernel/syscalls/swapon/swapon03.c
> @@ -25,7 +25,7 @@
>
> static int swapfiles;
>
> -static int setup_swap(void)
> +static void setup_swap(void)
> {
> pid_t pid;
> int status;
> @@ -54,33 +54,27 @@ static int setup_swap(void)
> TST_EXP_PASS_SILENT(swapon(filename, 0));
> }
> exit(0);
> - } else
> + } else {
> waitpid(pid, &status, 0);
> + }
>
> if (WEXITSTATUS(status))
> - tst_brk(TFAIL, "Failed to setup swap files");
> + tst_brk(TBROK, "Failed to setup swap files");
I wonder why do we run this code in a child process to begin with? This
is probably some leftover from the conversion to the new library. Among
other things this masks proper results propagation from the
MAKE_SMALL_SWAPFILE() because there is at least one tst_brk(TCONF, "")
in there that will be converted to TBROK here.
I guess that we want to remove the fork() here and we want SAFE_SWAPON()
instead of the TST_EXP_PASS_SILENT() so that we do tst_brk() if we fail
to setup the swapfile too. The TST_EXP_PASS_SILENT() does not end the
test on a failure, which is what we want here instead.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-11-11 13:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 16:34 [LTP] [PATCH v2 0/5] swapon03: Try to swapon() as many files until it fails Petr Vorel
2025-11-06 16:34 ` [LTP] [PATCH v2 1/5] swapon03: Don't create swap file twice Petr Vorel
2025-11-11 12:52 ` Cyril Hrubis
2025-11-11 15:24 ` Petr Vorel
2025-11-06 16:34 ` [LTP] [PATCH v2 2/5] swapon03: Cleanup Petr Vorel
2025-11-11 13:04 ` Cyril Hrubis [this message]
2025-11-11 15:47 ` Petr Vorel
2025-11-06 16:34 ` [LTP] [PATCH v2 3/5] swapon03: Try to swapon() as many files until it fails Petr Vorel
2025-11-07 3:15 ` Li Wang via ltp
2025-11-11 13:07 ` Cyril Hrubis
2025-11-11 15:58 ` Petr Vorel
2025-11-11 16:03 ` Petr Vorel
2025-11-06 16:34 ` [LTP] [PATCH v2 4/5] libswap: Remove now unused tst_max_swapfiles() Petr Vorel
2025-11-06 16:35 ` [LTP] [PATCH v2 5/5] swapon03: Remove grep dependency Petr Vorel
2025-11-07 16:27 ` Avinesh Kumar
2025-11-14 10:24 ` Petr Vorel
2025-11-14 10:27 ` Cyril Hrubis
2025-11-14 12:09 ` Petr Vorel
2025-11-14 14:38 ` Cyril Hrubis
2025-11-18 12:41 ` Petr Vorel
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=aRM0Z-IlZSLdB5ho@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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