Right. There's also the case where get_block() returns -EIO when,
for example, it fails on reading an indirect block. We end up
writing zeroes into some of the blocks. But I think that behaviour
is correct.
(I think I'll add a buffer_mapped() test to this code as well. It's
a bit redundant because the fs shouldn't go setting BH_New and not
BH_Mapped, but this code is _very_ rarely executed, and I haven't
tested all filesystems...)
@@ -1633,12 +1660,22 @@ static int __block_prepare_write(struct
*/
while(wait_bh > wait) {
wait_on_buffer(*--wait_bh);
- err = -EIO;
if (!buffer_uptodate(*wait_bh))
- goto out;
+ return -EIO;
}
return 0;
out:
+ bh = head;
+ block_start = 0;
+ do {
+ if (buffer_new(bh) && buffer_mapped(bh) && !buffer_uptodate(bh)) {
+ memset(kaddr+block_start, 0, bh->b_size);
+ set_bit(BH_Uptodate, &bh->b_state);
+ mark_buffer_dirty(bh);
+ }
+ block_start += bh->b_size;
+ bh = bh->b_this_page;
+ } while (bh != head);
return err;
}
I'll retest this, including the -EIO path.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/