Alexander Viro wrote:
... CUT ...
> diff -urN linux-ac19/fs/udf/file.c linux-ac19-fixes0/fs/udf/file.c
> --- linux-ac19/fs/udf/file.c Mon May 8 16:51:01 2000
> +++ linux-ac19-fixes0/fs/udf/file.c Sat Jun 17 01:05:00 2000
> @@ -115,9 +115,11 @@
> return 0;
> }
>
> +/* FIXME: block_sync_page() is wrong here */
> +
> struct address_space_operations udf_adinicb_aops = {
> - readpage: udf_adinicb_readpage,
> - writepage: udf_adinicb_writepage,
> + readpage: udf_adinicb_readpage,
> + writepage: udf_adinicb_writepage,
> sync_page: block_sync_page,
> prepare_write: udf_adinicb_prepare_write,
> commit_write: udf_adinicb_commit_write,
... CUT ...
Ok, what exactly needs to be done in sync_page.
Do I just need to write the inode (with its embedded data) to disk?
something like.. ?
int udf_adinicb_sync_page(struct page *)
{
struct inode *inode = (struct inode *)page->mapping->host;
return udf_sync_inode(inode);
}
Or is that too simple..
Thanks,
Ben
