On Thu, Jun 03, 2010 at 09:18:22AM +0200, Michael Kerrisk wrote: > Hi Pierre, > > On Wed, Jun 2, 2010 at 11:42 PM, Pierre Habouzit <madcoder@xxxxxxxxxx> wrote: > > On Mon, May 24, 2010 at 07:41:49PM +0200, Michael Kerrisk wrote: > >> Hello Pierre, > >> > >> On Tue, Apr 6, 2010 at 11:03 AM, Pierre Habouzit <madcoder@xxxxxxxxxx> wrote: > >> > See below a bug reported against the glibc. Since the glibc maintainer > >> > dodged that one, I assume the bug indeed is in the documentation of > >> > ftw(3). My manpages are the 3.24-1 Debian package. > >> > >> Yes. The man page is clearly incorrect. Thanks for reporting this. > >> > >> > IMHO the patch is: > >> > > >> > -fpath is the pathname of the entry relative to dirpath. > >> > +fpath is the pathname of the entry relative to the current working directory. > >> > > >> > POSIX is very vague about what "fpath" should be btw. > >> > >> (Agreed. It could be more precise.) > >> > >> I believe the correct text should be this: > >> > >> fpath is the pathname of the entry, and is > >> expressed either as a pathname relative to the > >> calling process's current working directory at the > >> time of the call to ftw(), if dirpath was expressed > >> as a relative pathname, or as an absolute pathname, > >> if dirpath was expressed as an absolute pathname. > >> > >> I have updated the man page accordingly, but would welcome > >> review/checking of this text. > > > > Afaict, it's not correct: ftw may perform chdir() calls, so the pathname > > is relative to the current working directory at the time `fn` is called. > > > > I'd rather phrase it that way (minus probable english mistakes): > > > > fpath is the pathname of the entry, and is either a relative > > pathname to the current working directory of the application when > > `fn` is called, or as an absolute pathname. > > Thanks for taking a look at this. However, I *think* your analysis is > wrong, and my proposed changes is right. But, still I'd like some > further confirmation. Please take a look at the the program below, and > the output produced when it runs. Yeah, that's because you're doing chdir()s during ftw, which is undefined behaviour as documented in the manpage already IIRC. The point is, ftw() /may/ decide to do chdir() by itself sometimes, and then the path is relative to the current working directory as set by ftw(). I'm pretty sure it's what POSIX authorizes ftw() to perform chdirs. And when I look at ftw.c in the glibc, it's also pretty much what happens in the case when you set FTW_CHDIR in the flags: ftw() forces a chdir before the fn() call, and makes the path relative to this cwd. It happens that the glibc doesn't seem to perform any kind of chdir() in the other cases (IOW when FTW_CHDIR isn't set), but I'm pretty sure POSIX allows ftw() to do so. -- ·O· Pierre Habouzit ··O madcoder@xxxxxxxxxx OOO http://www.madism.org -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
