[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220305124636.2002383-1-chenxiaosong2@huawei.com>
Date: Sat, 5 Mar 2022 20:46:34 +0800
From: ChenXiaoSong <chenxiaosong2@...wei.com>
To: <trond.myklebust@...merspace.com>, <anna@...nel.org>,
<smayhew@...hat.com>
CC: <linux-nfs@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<chenxiaosong2@...wei.com>, <liuyongqiang13@...wei.com>,
<yi.zhang@...wei.com>, <zhangxiaoxu5@...wei.com>
Subject: [PATCH -next 0/2] nfs: check writeback errors correctly
This series fixes nfs writeback error checking bugs.
If there is an error during the writeback process, it should be returned
when user space calls close() or fsync().
filemap_sample_wb_err() will return 0 if nobody has seen the error yet,
then filemap_check_wb_err() will return the unchanged writeback error.
ChenXiaoSong (2):
nfs: nfs{,4}_file_flush should consume writeback error
nfs: nfs_file_write() check writeback errors correctly
fs/nfs/file.c | 8 +++-----
fs/nfs/nfs4file.c | 4 +---
2 files changed, 4 insertions(+), 8 deletions(-)
--
2.31.1
Powered by blists - more mailing lists