On Fri, Jul 23, 2010 at 06:12:39PM +0200, Jan Kara wrote: > A reasonable mildly hacky solution would be to file inode against parent > filesystem's bdi if mapping->backing_dev isn't capable of having dirty > pages and do writeback and against mapping->backing_dev otherwise. This > would mean that we would have to properly mark bdis like the one of > /dev/zero as not capable of writeback. That seems like a good enough short term solution. In the long term this should be fixed as a side effect of some patches I'm about to submit. What I do is to split the writeback code (bdi_writeback and some fields currently in the backing_dev) off the backing_dev entirely an make them a separate entity. mapping->backing_dev will still point to the backing dev, but all inode dirtying and writeback will be done via the new sb->s_wb. -- 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
