Pekka J Enberg wrote:
We never want to _abort_ pending updates only pending reads. So, even with
revoke(), we need to be careful which is why we do do_fsync() in
generic_revoke_file() to make sure pending updates are flushed before we
declare the inode revoked.
But, I haven't looked at forced unmount that much so there may be other
issues I am not aware of.
For the purposes of this thread we _do_ want to abort pending updates to
force the system to give up on a broken block device rather than block a
bunch of tasks in the D state forever.
-
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
