On Tue, Aug 03, 2010 at 06:20:38PM +0200, Jan Kara wrote: > Background writeback and kupdate-style writeback are easily livelockable > (from a definition of their target). This is inconvenient because it can > make sync(1) stall forever waiting on its queued work to be finished. > Fix the problem by interrupting background and kupdate writeback if there > is some other work to do. We can return to them after completing all the > queued work. I don't think this is quite correct. If the only other callers was fsync_filesystems that would be true, but we also have the odd writeback_if_idle hack in ext4, and the bdi_start_writeback hack in laptop mode. -- 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
