From: Michael Menasherov via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3] read_all: Fix buffer too small for long paths
Date: Tue, 8 Sep 2026 12:22:48 +0300 [thread overview]
Message-ID: <20260908092248.15774-1-mmenashe@redhat.com> (raw)
queue_pop() copies each path into popped[BUFFER_SIZE], but BUFFER_SIZE
was 1024 while visit_dir() builds paths up to PATH_MAX. Any path longer
than 1023 bytes aborted the test with TBROK.
Use PATH_MAX for BUFFER_SIZE and MAX_PATH, and drop the extra -1 from
the queue_pop() bound so a PATH_MAX - 1 character path fits.
Tested on smaller boards and then on local machines with deeply nested
directories under /sys.
Fixes: 67c95fbbfc3a ("Add read_all file systems test")
Signed-off-by: Michael Menasherov <mmenashe@redhat.com>
---
testcases/kernel/fs/read_all/read_all.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/testcases/kernel/fs/read_all/read_all.c b/testcases/kernel/fs/read_all/read_all.c
index 5720ffb99..ec9454fc9 100644
--- a/testcases/kernel/fs/read_all/read_all.c
+++ b/testcases/kernel/fs/read_all/read_all.c
@@ -51,8 +51,8 @@
#include "tst_timer.h"
#define QUEUE_SIZE 16384
-#define BUFFER_SIZE 1024
-#define MAX_PATH 4096
+#define BUFFER_SIZE PATH_MAX
+#define MAX_PATH PATH_MAX
#define MAX_DISPLAY 40
struct queue {
@@ -131,7 +131,7 @@ static int queue_pop(struct queue *q)
while (q->data[i]) {
q->popped[j] = q->data[i];
- if (++j >= BUFFER_SIZE - 1)
+ if (++j >= BUFFER_SIZE)
tst_brk(TBROK, "Buffer is too small for path");
i = (i + 1) % QUEUE_SIZE;
--
2.55.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2026-09-08 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 9:22 Michael Menasherov via ltp [this message]
2026-09-08 10:42 ` [LTP] read_all: Fix buffer too small for long paths linuxtestproject.agent
2026-09-11 7:17 ` [LTP] [PATCH v3] " 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=20260908092248.15774-1-mmenashe@redhat.com \
--to=ltp@lists.linux.it \
--cc=mmenashe@redhat.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.