Re: ramfs problem... (unlink of sparse file in "D" state)

[Stefan Traby]

On Mon, Jan 08, 2001 at 01:05:49PM -0500, Alexander Viro wrote:
> 
> 
> On Mon, 8 Jan 2001, Stefan Traby wrote:
> 
> > On Mon, Jan 08, 2001 at 04:01:10PM +0000, Alan Cox wrote:
> > > > I prefer SuS fpathconf(), pathconf() is just a wrapper to fpathconf();
> > > 
> > > You can't implement it that way in the corner cases.
> > 
> > I reread SuSv2 again and didn't found corner cases.
> > Do you mean FIFO/pipe stuff ? I can't see the problem in this area.
> > 
> > In which case is an emulation of pathconf by fpathconf impossible ?
> 
> Damnit, symlinks for one thing.

No this is no problem.

 For pathconf(), the path argument points to the pathname of a file
      or directory.

IMHO lstat can dedect this case.
Where is the problem ?
Calling pathconf with a symlink is not defined. I suggest
an implementation of "yankee doodle" for that case.
Anyway the broken SuS standard wants that pathconf follow symlinks.
Or how do you interpret this:

 [ELOOP]
           Too many symbolic links were encountered in resolving path.

But Alan's case "out of filedescriptor" fully counts.
Anyway, I personally would ignore it, but I agree, it's a completely
valid argument.

-- 

  ciao - 
    Stefan

"     ( cd /lib ; ln -s libBrokenLocale-2.2.so libNiedersachsen.so )     "
    
Stefan Traby                Linux/ia32               fax:  [phone]
Mitterlasznitzstr. 13       Linux/alpha            phone:  [phone]
8302 Nestelbach             Linux/sparc       http://www.hello-penguin.com
Austria                                    mailto://[e-mail]
Europe                                   mailto://[e-mail]