From: Petr Vorel <pvorel@suse.cz>
To: Jinseok Kim <always.starving0@gmail.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4] close02: add test for double close EBADF
Date: Fri, 17 Apr 2026 13:56:48 +0200 [thread overview]
Message-ID: <20260417115648.GC409289@pevik> (raw)
In-Reply-To: <20260416125554.2920-1-always.starving0@gmail.com>
Hi Jinseok,
...
> -static void run(void)
> +static struct tcase {
> + const char *desc;
> + int fd;
> + int exp_errno;
> +} tcases[] = {
> + { "close(-1)", -1, EBADF },
> + { "close same fd twice", -1, EBADF },
> +};
> +
> +static void verify_close(unsigned int i)
> +{
> + struct tcase *tc = &tcases[i];
> +
> + TST_EXP_FAIL(close(tc->fd), tc->exp_errno, "%s", tc->desc);
> +}
> +
> +static void setup(void)
> {
> - TST_EXP_FAIL(close(-1), EBADF);
> + int fd = SAFE_OPEN("close02", O_CREAT | O_RDWR, 0600);
> +
> + SAFE_CLOSE(fd);
> + tcases[1].fd = fd;
Depending on index is error-prone. I know that test array has only 2 members,
but could you please use our usual approach to use file descriptors as static?
See fd_ebadf and fd_enotdir in testcases/kernel/syscalls/bind/bind01.c.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-04-17 11:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 13:30 [LTP] [PATCH 1/2] close: remove unused headers and fix minor style issues Jinseok Kim
2026-04-06 13:31 ` [LTP] [PATCH 2/2] close: add test for double close EBADF Jinseok Kim
2026-04-09 8:15 ` Petr Vorel
2026-04-11 11:04 ` [LTP] [PATCH v2] " Jinseok Kim
2026-04-13 4:33 ` Li Wang
2026-04-13 11:30 ` Petr Vorel
2026-04-13 16:52 ` [LTP] [PATCH v3] " Jinseok Kim
2026-04-13 18:04 ` [LTP] " linuxtestproject.agent
2026-04-13 20:45 ` [LTP] [PATCH v3] " Petr Vorel
2026-04-16 12:55 ` [LTP] [PATCH v4] close02: " Jinseok Kim
2026-04-16 13:44 ` [LTP] " linuxtestproject.agent
2026-04-17 0:01 ` [LTP] [PATCH v4] " Li Wang
2026-04-17 11:56 ` Petr Vorel [this message]
2026-04-09 8:08 ` [LTP] [PATCH 1/2] close: remove unused headers and fix minor style issues 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=20260417115648.GC409289@pevik \
--to=pvorel@suse.cz \
--cc=always.starving0@gmail.com \
--cc=ltp@lists.linux.it \
/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