From: Trond Myklebust <trondmy@gmail.com>
To: Su Yanjun <suyj.fnst@cn.fujitsu.com>,
Anna Schumaker <Anna.Schumaker@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v2 0/2] Fix O_DIRECT error handling
Date: Tue, 1 Oct 2019 16:19:58 -0400 [thread overview]
Message-ID: <20191001202000.13248-1-trond.myklebust@hammerspace.com> (raw)
These patches fix issues with how O_DIRECT handles read and write
errors, and also how it handles eof.
v2:
- Change to handle all short reads and writes in the same manner.
Note that we can still end up breaking generic/465 by using the
nconnect=<n> (where n > 1) mount option. The reason is that the
test assumes the writes land in increasing order on the server,
despite having being launched in parallel.
Trond Myklebust (2):
NFS: Fix O_DIRECT accounting of number of bytes read/written
NFS: Remove redundant mirror tracking in O_DIRECT
fs/nfs/direct.c | 111 ++++++++++++++++++------------------------------
1 file changed, 41 insertions(+), 70 deletions(-)
--
2.21.0
next reply other threads:[~2019-10-01 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 20:19 Trond Myklebust [this message]
2019-10-01 20:19 ` [PATCH v2 1/2] NFS: Fix O_DIRECT accounting of number of bytes read/written Trond Myklebust
2019-10-01 20:20 ` [PATCH v2 2/2] NFS: Remove redundant mirror tracking in O_DIRECT Trond Myklebust
2019-10-08 8:11 ` [PATCH v2 1/2] NFS: Fix O_DIRECT accounting of number of bytes read/written Su Yanjun
2019-10-08 12:42 ` Trond Myklebust
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=20191001202000.13248-1-trond.myklebust@hammerspace.com \
--to=trondmy@gmail.com \
--cc=Anna.Schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=suyj.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).