Messages in this thread |  | | Date | Mon, 8 Jan 2001 07:16:25 -0500 (EST) | From | Alexander Viro <> | Subject | Re: ramfs problem... (unlink of sparse file in "D" state) |
| |
On Mon, 8 Jan 2001, Alan Cox wrote:
> > > 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.
Umm... Details, please? Are you talking about 2^32 or about fs layout limits? The former may very well belong to VFS - no arguments here. The latter... And yes, fs layout limits are visible - for ext2 they can be as low as 2^24 blocks.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |