On Wed, Feb 07, 2007 at 01:00:28PM +0000, Hugh Dickins wrote: > On Wed, 7 Feb 2007, David Chinner wrote: > > > On Christoph's suggestion, take the guts of the proposed > > xfs_vm_page_mkwrite function and implement it as a generic > > core function as it used no specific XFS code at all. > > > > This allows any filesystem to easily hook the ->page_mkwrite() > > VM callout to allow them to set up pages dirtied by mmap > > writes correctly for later writeout. > > > > Signed-Off-By: Dave Chinner <dgc@xxxxxxx> > > I'm worried about concurrent truncation. Isn't it the case that > i_mutex is held when prepare_write and commit_write are normally > called? But not here when page_mkwrite is called. I'm not holding i_mutex. I assumed that it was probably safe to do because we are likely to be reading the page off disk just before we call mkwrite and that has to be synchronised with truncate in some manner.... So, do I need to grab the i_mutex here? Is that safe to do that in the middle of a page fault? If we do race with a truncate and the page is now beyond EOF, what am I supposed to return? I'm fishing for what I'm supposed to be doing here because there's zero implementations of this callout in the kernel and the comments in the code explaining the interface constraints are non-existant.... Cheers, Dave. -- Dave Chinner Principal Engineer SGI Australian Software Group - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
