Re: [RFC PATCH 0/3] Stop clearing uptodate flag on write IO error
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: 2012-01-17 00:59:41
Also in:
linux-fsdevel, lkml
On Mon, Jan 16, 2012 at 4:36 PM, Dave Chinner [off-list ref] wrote:
Jan is right, Linus. His definition of what up-to-date means for dirty buffers is correct, especially in the case of write errors.
It's not a dirty buffer any more.
Go look. We've long since cleared the dirty bit.
So stop spouting garbage.
My argument is simple: the contents ARE NOT CORRECT ENOUGH to be
called "up-to-date and clean".
And I outlined the two choices:
- mark it dirty and continue trying to write it out forever
- invalidate it.
Anything else is crazy talk. And marking it dirty forever isn't really
an option. So..
Linus