Re: [PATCH v2 11/21] exfat: check for a directory write error with buffer_write_io_error()

[Jan Kara]

On Thu 06-08-26 12:58:34, Chao Shi wrote:
> exfat_update_bhs() waits for the writes it issued and then tests
> !buffer_uptodate() to find the ones that failed.  That relies on the write
> completion handler clearing BH_Uptodate on error, which this series
> removes: a buffer whose write failed still holds the data the filesystem
> asked to be written, so declaring it not up to date is wrong and makes
> callers re-read it.
> 
> Test BH_Write_EIO, which is what the completion handler sets and what this
> code actually wants to know.
> 
> No behaviour change today - a failed write sets BH_Write_EIO and clears
> BH_Uptodate together.  It stops being a no-op at the end of the series,
> where the new test is the one that still works.
> 
> Acked-by: Weidong Zhu <weizhu@xxxxxxx>
> Signed-off-by: Chao Shi <coshi036@xxxxxxxxx>

Looks good. Feel free to add:

Reviewed-by: Jan Kara <jack@xxxxxxx>

								Honza

> ---
>  fs/exfat/misc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/exfat/misc.c b/fs/exfat/misc.c
> index 6f11a96a4ffa..dfd0bbf31c94 100644
> --- a/fs/exfat/misc.c
> +++ b/fs/exfat/misc.c
> @@ -187,7 +187,7 @@ int exfat_update_bhs(struct buffer_head **bhs, int nr_bhs, int sync)
>  
>  	for (i = 0; i < nr_bhs && sync; i++) {
>  		wait_on_buffer(bhs[i]);
> -		if (!err && !buffer_uptodate(bhs[i]))
> +		if (!err && buffer_write_io_error(bhs[i]))
>  			err = -EIO;
>  	}
>  	return err;
> -- 
> 2.43.0
> 
-- 
Jan Kara <jack@xxxxxxxx>
SUSE Labs, CR