From: Joakim Sindholt <opensource@zhasha.com>
To: musl@lists.openwall.com
Subject: nftw miscalculates FTW.base when pathnames end in /
Date: Wed, 04 May 2016 15:42:19 +0200 [thread overview]
Message-ID: <1462369339.29574.1@mail.zhasha.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1675 bytes --]
Running the test program from the glibc ftw man page[1]:
+zhasha@wirbelwind /home/zhasha ; ./6.out test
d 0 4096 test 0 test
d 1 4096 test/a 5 a
f 2 0 test/a/1 7 1
d 1 4096 test/b 5 b
f 2 0 test/b/1 7 1
f 2 0 test/b/2 7 2
d 1 4096 test/ddd 5 ddd
f 2 0 test/ddd/5 9 5
d 1 4096 test/cc 5 cc
f 2 0 test/cc/3 8 3
+zhasha@wirbelwind /home/zhasha ; ./6.out test/
d 0 4096 test/ 4 /
d 1 4096 test/a 6
f 2 0 test/a/1 7 1
d 1 4096 test/b 6
f 2 0 test/b/1 7 1
f 2 0 test/b/2 7 2
d 1 4096 test/ddd 6 dd
f 2 0 test/ddd/5 9 5
d 1 4096 test/cc 6 c
f 2 0 test/cc/3 8 3
The final 2 columns are the file name length and path + ftw->base
respectively, which is off by one when the path ends in /. It also
seems to confuse the initial dir name.
I have attached a fix but I'm not sure it's a particularly good one.
[1] http://linux.die.net/man/3/ftw
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: nftw.patch --]
[-- Type: text/x-patch, Size: 563 bytes --]
diff --git a/src/misc/nftw.c b/src/misc/nftw.c
index efb2b89..7c2c0d3 100644
--- a/src/misc/nftw.c
+++ b/src/misc/nftw.c
@@ -108,11 +108,13 @@ int nftw(const char *path, int (*fn)(const char *, const struct stat *, int, str
if (fd_limit <= 0) return 0;
l = strlen(path);
+ while (l && path[l-1]=='/') --l;
if (l > PATH_MAX) {
errno = ENAMETOOLONG;
return -1;
}
- memcpy(pathbuf, path, l+1);
+ memcpy(pathbuf, path, l);
+ pathbuf[l]='\0';
pthread_setcancelstate(PTHREAD_CANCEL_DISABLE, &cs);
r = do_nftw(pathbuf, fn, fd_limit, flags, NULL);
next reply other threads:[~2016-05-04 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 13:42 Joakim Sindholt [this message]
2016-05-14 3:01 ` Rich Felker
2016-07-12 9:41 ` Joakim Sindholt
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=1462369339.29574.1@mail.zhasha.com \
--to=opensource@zhasha.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).