On Thu, Jun 04, 2009 at 11:40:03AM +0530, Aneesh Kumar K.V wrote: > Even with changes to make pages writeprotect on truncate/i_size update we > can still see buffer_heads which are not mapped in the writepage > callback. Which changes were you referring to here? Do you mean Jan's patch page_mkwrite()'s changes, or something else? Also it seems like: ext4: Merge ext4_{journalled,normal,da}_writepage() into ext4_writepage() might be a better patch title, do you agree? > 1) truncate(f, 1024) > 2) mmap(f, 0, 4096) > 3) a[0] = 'a' > 4) truncate(f, 4096) > 5) writepage(...) > > Now if we get a writepage callback immediately after (4) and before an > attempt to write at any other offset via mmap address (which implies we > are yet to get a pagefault and do a get_block) what we would have is the > page which is dirty have first block allocated and the other three > buffer_heads unmapped. The first two paragraps of this description are the same as the previous patch; so really what's happening here is this fixes the same issue as the previous patch, but for the the case where delayed allocation is not enabled, is that correct? - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html