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

[Alan Cox]

> > I put it into generic_file_write. That covers most fs's it seems. The jffs 
> > guys are going to switch to generic_file_write soon and the other fs's 
> > that dont are wacko ones I dont care about ;)
> 
> Alan, we have to deal with get_block() failures anyway. -ENOSPC, -EDQUOT,
> not to mention plain and simple -EIO. -EFBIG handling is not different.

EFBIG is very different in several ways. To start with the get_block code
doesnt have enough information to correctly implement the SUS specification
rules.

The generic cases can be handled in generic code. They cannot cleanly be
handled by copying that code into every file system. Ditto with truncate.
Since the VFS can handle them nicely the VFS should handle them.

Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/