From: Al Viro <viro@zeniv.linux.org.uk>
To: ltp@lists.linux.it
Cc: linux-fsdevel@vger.kernel.org
Subject: [LTP][PATCH] lack of ENAMETOOLONG testcases for pathnames longer than PATH_MAX
Date: Tue, 13 Jan 2026 19:49:36 +0000 [thread overview]
Message-ID: <20260113194936.GQ3634291@ZenIV> (raw)
There are different causes of ENAMETOOLONG. It might come from
filesystem rejecting an excessively long pathname component, but there's
also "pathname is longer than PATH_MAX bytes, including terminating NUL"
and that doesn't get checked anywhere.
Ran into that when a braino in kernel patch broke that logics
(ending up with cutoff too low) and that didn't get caught by LTP run.
Patch below adds the checks to one of the tests that do deal
with the other source of ENAMETOOLONG; it almost certainly not the
right use of infrastructure, though.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
---
diff --git a/testcases/kernel/syscalls/chdir/chdir04.c b/testcases/kernel/syscalls/chdir/chdir04.c
index 6e53b7fef..e8dd5121d 100644
--- a/testcases/kernel/syscalls/chdir/chdir04.c
+++ b/testcases/kernel/syscalls/chdir/chdir04.c
@@ -11,6 +11,8 @@
#include "tst_test.h"
static char long_dir[] = "abcdefghijklmnopqrstmnopqrstuvwxyzabcdefghijklmnopqrstmnopqrstuvwxyzabcdefghijklmnopqrstmnopqrstuvwxyzabcdefghijklmnopqrstmnopqrstuvwxyzabcdefghijklmnopqrstmnopqrstuvwxyzabcdefghijklmnopqrstmnopqrstuvwxyzabcdefghijklmnopqrstmnopqrstuvwxyzabcdefghijklmnopqrstmnopqrstuvwxyz";
+static char long_path[PATH_MAX+1];
+static char shorter_path[PATH_MAX];
static char noexist_dir[] = "noexistdir";
static struct tcase {
@@ -20,16 +22,23 @@ static struct tcase {
{long_dir, ENAMETOOLONG},
{noexist_dir, ENOENT},
{0, EFAULT}, // bad_addr
+ {long_path, ENAMETOOLONG},
+ {shorter_path, 0},
};
static void verify_chdir(unsigned int i)
{
- TST_EXP_FAIL(chdir(tcases[i].dir), tcases[i].exp_errno, "chdir()");
+ if (tcases[i].exp_errno)
+ TST_EXP_FAIL(chdir(tcases[i].dir), tcases[i].exp_errno, "chdir()");
+ else
+ TST_EXP_PASS(chdir(tcases[i].dir), "chdir()");
}
static void setup(void)
{
tcases[2].dir = tst_get_bad_addr(NULL);
+ memset(long_path, '/', PATH_MAX);
+ memset(shorter_path, '/', PATH_MAX - 1);
}
static struct tst_test test = {
next reply other threads:[~2026-01-13 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 19:49 Al Viro [this message]
2026-01-14 8:35 ` [LTP] [PATCH] lack of ENAMETOOLONG testcases for pathnames longer than PATH_MAX Andrea Cervesato
2026-01-14 8:37 ` Andrea Cervesato
2026-01-14 14:30 ` Al Viro
2026-01-14 14:38 ` Andrea Cervesato
2026-01-14 9:40 ` Cyril Hrubis
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=20260113194936.GQ3634291@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--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