[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1JaGsN-00055L-Df@pomaz-ex.szeredi.hu>
Date: Fri, 14 Mar 2008 21:51:39 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: staubach@...hat.com
CC: miklos@...redi.hu, drepper@...hat.com, viro@...IV.linux.org.uk,
bharata@...ux.vnet.ibm.com, libc-alpha@...rceware.org,
jblunck@...e.de, ezk@...sunysb.edu, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, hch@....de, cmm@...ibm.com,
haveblue@...ibm.com
Subject: Re: [RFC] Union mount readdir support in glibc
> >>> Actually, do we really need it other than to 0 and to current position
> >>> (i.e. full rewind and a no-op)?
> >>>
> >> Ever heard of the little function "telldir"?
> >>
> >
> > Actually, telldir/seekdir is already broken for some filesystems (NFS
> > comes to mind). POSIX was really crazy to require a working seekdir
> > implementation, and userspace should quickly start _not_ using it.
> >
> >
>
> What makes you think that telldir/seekdir don't work for NFS?
http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/5124
It turned out to be due to incorrect NFS behavior if files are removed
between telldir and seekdir.
So it does work sometimes, but does not seem to correctly handle all
cases. I have no idea if this is an issue in the server, the client
or the protocol.
What is certain, is that seekdir/telldir is a really bad interface,
that just makes life difficult for filesystem implementors, without
any real gain. It deserves to die.
Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists