mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ChenXiaoSong <chenxiaosong2@huawei.com>
To: <trond.myklebust@hammerspace.com>, <anna@kernel.org>,
	<smayhew@redhat.com>
Cc: <linux-nfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<chenxiaosong2@huawei.com>, <liuyongqiang13@huawei.com>,
	<yi.zhang@huawei.com>, <zhangxiaoxu5@huawei.com>
Subject: [PATCH -next,v2 0/3] nfs: handle writeback errors correctly
Date: Fri, 1 Apr 2022 11:44:06 +0800	[thread overview]
Message-ID: <20220401034409.256770-1-chenxiaosong2@huawei.com> (raw)

v1:
cover letter: (nfs: check writeback errors correctly)

v2:
- return more nuanced writeback errors in nfs_file_write().
- return writeback error in close()->flush() without consumed it.
- fix: nfs_file_write() will always call nfs_wb_all() even if there is no
new writeback error.


ChenXiaoSong (3):
  NFS: return more nuanced writeback errors in nfs_file_write()
  NFS: nfs{,4}_file_flush() return correct writeback errors
  Revert "nfs: nfs_file_write() should check for writeback errors"

 fs/nfs/file.c     | 23 ++++++++++-------------
 fs/nfs/nfs4file.c |  8 ++++----
 fs/nfs/write.c    |  5 +----
 3 files changed, 15 insertions(+), 21 deletions(-)

-- 
2.31.1


             reply	other threads:[~2022-04-01  3:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  3:44 ChenXiaoSong [this message]
2022-04-01  3:44 ` [PATCH -next,v2 1/3] NFS: return more nuanced writeback errors in nfs_file_write() ChenXiaoSong
2022-04-01  3:44 ` [PATCH -next,v2 2/3] NFS: nfs{,4}_file_flush() return correct writeback errors ChenXiaoSong
2022-04-01  3:44 ` [PATCH -next,v2 3/3] Revert "nfs: nfs_file_write() should check for writeback errors" ChenXiaoSong
2022-04-01  7:03 ` [PATCH -next,v2 0/3] nfs: handle writeback errors correctly chenxiaosong (A)
2022-04-11 14:15   ` chenxiaosong (A)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220401034409.256770-1-chenxiaosong2@huawei.com \
    --to=chenxiaosong2@huawei.com \
    --cc=anna@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=liuyongqiang13@huawei.com \
    --cc=smayhew@redhat.com \
    --cc=trond.myklebust@hammerspace.com \
    --cc=yi.zhang@huawei.com \
    --cc=zhangxiaoxu5@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®