Hi Nick, I'm still working on the bug in http://bugzilla.kernel.org/show_bug.cgi?id=12913 . One other source of grief appears to be munmap(), which is calling set_page_dirty() on a number of pages without locking them or first calling page_mkwrite(). Currently, this means that we either ignore that dirty bit (since nfs_page_async_flush() won't find a corresponding write request) or it too can end up triggering the PG_CLEAN BUG() in fs/nfs/write.c:252 if the timing is right. So what is the reason why zap_pte_range() calls set_page_dirty() directly? Cheers Trond -- 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
