Messages in this thread |  | | Subject | Re: ramfs problem... (unlink of sparse file in "D" state) | Date | Mon, 8 Jan 2001 11:46:53 +0000 (GMT) | From | Alan Cox <> |
| |
> Alan, it doesn't work that way. Maximal size depends on the type of object, > for one thing. Moreover, it's not always a multiple of page size, so you
Its a multiple of page size for all fs's we have but I did it in terms of bytes anyway
> still need foo_get_block() to be aware of the problem (it should return > -EFBIG). Besides, we need to take care of the situations when some of > get_block() calls fail in prepare_write() - that can happen due to other > problems. I've fixed all that stuff for ext2 (check the patches posted on > l-k after 12-pre6). We need to propagate it into other filesystems, but
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 ;)
- 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/
|  |