From: Jinseok Kim <always.starving0@gmail.com>
To: pvorel@suse.cz
Cc: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] close: add test for double close EBADF
Date: Sat, 11 Apr 2026 20:04:03 +0900 [thread overview]
Message-ID: <20260411110405.7330-1-always.starving0@gmail.com> (raw)
In-Reply-To: <20260409081546.GB96667@pevik>
Verify that calling close() on an already closed file descriptor fails
with EBADF.
This test adds coverage for a common state transition case where a
previously valid file descriptor becomes invalid after close().
Signed-off-by: Jinseok Kim <always.starving0@gmail.com>
---
Changes in v2:
- Add additional test coverage to close02 instead of creating a separate
close03 test.
- Link to v1: https://lore.kernel.org/ltp/20260406133134.17238-2-always.starving0@gmail.com
---
testcases/kernel/syscalls/close/close02.c | 42 ++++++++++++++++++++---
1 file changed, 38 insertions(+), 4 deletions(-)
diff --git a/testcases/kernel/syscalls/close/close02.c b/testcases/kernel/syscalls/close/close02.c
index 617c48237..768361e56 100644
--- a/testcases/kernel/syscalls/close/close02.c
+++ b/testcases/kernel/syscalls/close/close02.c
@@ -5,17 +5,51 @@
*/
/*\
- * Call close(-1) and expects it to return EBADF.
+ * Verify :manpage:`close(2)` failure cases:
+ *
+ * 1) close(-1) returns EBADF.
+ * 2) closing the same fd twice returns EBADF on the second call.
*/
#include <errno.h>
+#include <fcntl.h>
+
#include "tst_test.h"
-static void run(void)
+enum case_type {
+ INVALID_FD,
+ DOUBLE_CLOSE,
+};
+
+static struct tcase {
+ const char *desc;
+ enum case_type type;
+} tcases[] = {
+ { "close(-1)", INVALID_FD },
+ { "close same fd twice", DOUBLE_CLOSE },
+};
+
+static void verify_close(unsigned int i)
{
- TST_EXP_FAIL(close(-1), EBADF);
+ int fd;
+ struct tcase *tc = &tcases[i];
+
+ switch (tc->type) {
+ case INVALID_FD:
+ TST_EXP_FAIL(close(-1), EBADF, "%s", tc->desc);
+ break;
+
+ case DOUBLE_CLOSE:
+ fd = SAFE_OPEN("close02", O_CREAT, 0600);
+
+ TST_EXP_PASS(close(fd), "%s: first close()", tc->desc);
+ TST_EXP_FAIL(close(fd), EBADF, "%s: second close()", tc->desc);
+ break;
+ }
}
static struct tst_test test = {
- .test_all = run,
+ .needs_tmpdir = 1,
+ .tcnt = ARRAY_SIZE(tcases),
+ .test = verify_close,
};
--
2.43.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-04-11 11:04 UTC|newest]
Thread overview: 5+ 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 ` Jinseok Kim [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=20260411110405.7330-1-always.starving0@gmail.com \
--to=always.starving0@gmail.com \
--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