-
由 Jeff Layton 提交于
When a loop block device encounters a writeback error, that error will get propagated to the bd_inode's wb_err field. If we then detach the backing file from it, attach another and fsync it, we'll get back the writeback error that we had from the previous backing file. This is a bit of a grey area as POSIX doesn't cover loop devices, but it is somewhat counterintuitive. If we detach a backing file from the loopdev while there are still unreported errors, take it as a sign that we're no longer interested in the previous file, and clear out the wb_err in the loop blockdev. Reported-and-Tested-by: NTheodore Y. Ts'o <tytso@mit.edu> Signed-off-by: NJeff Layton <jlayton@redhat.com> Signed-off-by: NJens Axboe <axboe@kernel.dk>
eedffa28