All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wake Liu via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Cc: Wake Liu <wakel@google.com>
Subject: [LTP] [PATCH] pathconf01: Allow EINVAL where POSIX leaves support unspecified
Date: Mon,  5 Oct 2026 06:19:33 +0000	[thread overview]
Message-ID: <20261005061933.4108985-1-wakel@google.com> (raw)

POSIX lists two EINVAL cases for pathconf(). It shall fail with EINVAL
when the value of name is not valid. It may also fail with EINVAL when
"the implementation does not support an association of the variable
name with the specified file".

The test always calls pathconf() on a directory. For a directory, POSIX
leaves it unspecified whether _PC_MAX_CANON, _PC_MAX_INPUT and
_PC_VDISABLE (note 2), _PC_ASYNC_IO, _PC_PRIO_IO and _PC_SYNC_IO
(note 8) and the _PC_REC_* names (note 10) are supported, so EINVAL is
allowed for them.

Bionic before Android 15 returns -1 and sets errno to EINVAL for
_PC_REC_INCR_XFER_SIZE and _PC_REC_MAX_XFER_SIZE, which makes the test
fail.

Report EINVAL as TCONF for these names. EINVAL for the other names is
still a failure.

Also print the name and errno on failure, so it is clear which name
failed.

Signed-off-by: Wake Liu <wakel@google.com>
---
 .../kernel/syscalls/pathconf/pathconf01.c     | 36 ++++++++++++-------
 1 file changed, 23 insertions(+), 13 deletions(-)

diff --git a/testcases/kernel/syscalls/pathconf/pathconf01.c b/testcases/kernel/syscalls/pathconf/pathconf01.c
index 5af45e417..635c356bc 100644
--- a/testcases/kernel/syscalls/pathconf/pathconf01.c
+++ b/testcases/kernel/syscalls/pathconf/pathconf01.c
@@ -19,24 +19,26 @@ static char *path;
 static struct tcase {
 	int value;
 	char *name;
+	/* POSIX leaves support for a directory unspecified */
+	int einval_ok;
 } tcases[] = {
 	{NAME_DESC(_PC_LINK_MAX)},
-	{NAME_DESC(_PC_MAX_CANON)},
-	{NAME_DESC(_PC_MAX_INPUT)},
+	{NAME_DESC(_PC_MAX_CANON), .einval_ok = 1},
+	{NAME_DESC(_PC_MAX_INPUT), .einval_ok = 1},
 	{NAME_DESC(_PC_NAME_MAX)},
 	{NAME_DESC(_PC_PATH_MAX)},
 	{NAME_DESC(_PC_PIPE_BUF)},
 	{NAME_DESC(_PC_CHOWN_RESTRICTED)},
 	{NAME_DESC(_PC_NO_TRUNC)},
-	{NAME_DESC(_PC_VDISABLE)},
-	{NAME_DESC(_PC_SYNC_IO)},
-	{NAME_DESC(_PC_ASYNC_IO)},
-	{NAME_DESC(_PC_PRIO_IO)},
+	{NAME_DESC(_PC_VDISABLE), .einval_ok = 1},
+	{NAME_DESC(_PC_SYNC_IO), .einval_ok = 1},
+	{NAME_DESC(_PC_ASYNC_IO), .einval_ok = 1},
+	{NAME_DESC(_PC_PRIO_IO), .einval_ok = 1},
 	{NAME_DESC(_PC_FILESIZEBITS)},
-	{NAME_DESC(_PC_REC_INCR_XFER_SIZE)},
-	{NAME_DESC(_PC_REC_MAX_XFER_SIZE)},
-	{NAME_DESC(_PC_REC_MIN_XFER_SIZE)},
-	{NAME_DESC(_PC_REC_XFER_ALIGN)},
+	{NAME_DESC(_PC_REC_INCR_XFER_SIZE), .einval_ok = 1},
+	{NAME_DESC(_PC_REC_MAX_XFER_SIZE), .einval_ok = 1},
+	{NAME_DESC(_PC_REC_MIN_XFER_SIZE), .einval_ok = 1},
+	{NAME_DESC(_PC_REC_XFER_ALIGN), .einval_ok = 1},
 };
 
 static void verify_pathconf(unsigned int i)
@@ -47,10 +49,18 @@ static void verify_pathconf(unsigned int i)
 
 	TEST(pathconf(path, tc->value));
 
-	if (TST_RET == -1 && errno != 0)
-		tst_res(TFAIL, "pathconf Failed, errno = %d", TST_ERR);
-	else
+	if (TST_RET != -1 || !TST_ERR) {
 		tst_res(TPASS, "pathconf(%s, %s)", path, tc->name);
+		return;
+	}
+
+	if (tc->einval_ok && TST_ERR == EINVAL) {
+		tst_res(TCONF, "pathconf(%s, %s) not supported for a directory",
+			path, tc->name);
+		return;
+	}
+
+	tst_res(TFAIL | TTERRNO, "pathconf(%s, %s)", path, tc->name);
 }
 
 static struct tst_test test = {
-- 
2.56.0.rc1.315.gc6ed9934b7-goog


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

             reply	other threads:[~2026-10-05  6:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05  6:19 Wake Liu via ltp [this message]
2026-10-05  8:28 ` [LTP] pathconf01: Allow EINVAL where POSIX leaves support unspecified linuxtestproject.agent
2026-10-12 16:20 ` [LTP] [PATCH] " Andrea Cervesato via ltp
2026-10-13 13:45   ` Wake Liu via ltp
2026-10-13 14:37     ` Andrea Cervesato via ltp
2026-10-13 14:40 ` 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=20261005061933.4108985-1-wakel@google.com \
    --to=ltp@lists.linux.it \
    --cc=wakel@google.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.