[PATCH] async write errors: fix spurious fs truncate errors
From: Oliver Xymoron <oxymoron@waste.org> Currently, a writepage() which detects that it is writing outside i_size (due to concurrent truncate) will abandon the write, returning -EIO. The return value will bogusly cause an error to be recorded in the address_space. So convert all those writepage() instances to return zero in this case.
Showing
Please register or sign in to comment