linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, jack@suse.cz, khazhy@google.com,
	Gabriel Krisman Bertazi <krisman@collabora.com>,
	kernel@collabora.com
Subject: [PATCH v2 0/3] Unaligned DIO read error path fix and clean ups
Date: Thu,  3 Sep 2020 16:04:11 -0400	[thread overview]
Message-ID: <20200903200414.673105-1-krisman@collabora.com> (raw)

Hi,

This follows up on my previous submision of "direct-io: defer alignment
check until after the EOF check".  This version applies the suggestions
from Jan Kara (thank you!) and it was tested with xfstests aio group
over f2fs and fio workloads.

Gabriel Krisman Bertazi (3):
  direct-io: clean up error paths of do_blockdev_direct_IO
  direct-io: don't force writeback for reads beyond EOF
  direct-io: defer alignment check until after the EOF check

 fs/direct-io.c | 64 ++++++++++++++++++++++++--------------------------
 1 file changed, 31 insertions(+), 33 deletions(-)

-- 
2.28.0


             reply	other threads:[~2020-09-03 20:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 20:04 Gabriel Krisman Bertazi [this message]
2020-09-03 20:04 ` [PATCH v2 1/3] direct-io: clean up error paths of do_blockdev_direct_IO Gabriel Krisman Bertazi
2020-09-04  7:47   ` Jan Kara
2020-09-03 20:04 ` [PATCH v2 2/3] direct-io: don't force writeback for reads beyond EOF Gabriel Krisman Bertazi
2020-09-04  7:48   ` Jan Kara
2020-09-03 20:04 ` [PATCH v2 3/3] direct-io: defer alignment check until after the EOF check Gabriel Krisman Bertazi
2020-09-04  7:49   ` Jan Kara

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=20200903200414.673105-1-krisman@collabora.com \
    --to=krisman@collabora.com \
    --cc=jack@suse.cz \
    --cc=kernel@collabora.com \
    --cc=khazhy@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).