linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs updates for 5.8, part 2
Date: Sun, 14 Jun 2020 13:56:05 +0200	[thread overview]
Message-ID: <cover.1592135316.git.dsterba@suse.com> (raw)

Hi,

this reverts the direct io port to iomap infrastructure of btrfs merged
in the first pull request. We found problems in invalidate page that
don't seem to be fixable as regressions or without changing iomap code
that would not affect other filesystems.

There are 4 patches reverted in total, but 3 of them are followup
cleanups needed to revert a43a67a2d715540c13 cleanly. The result is the
buffer head based implementation of direct io.

There's one trivial conflict that git does not auto-resolve, in the
address space operations readpages has been replaced by readahead and
this change is in the context of the direct io callback diff.

Reverts are not great, but under current circumstances I don't see
better options. Please pull, thanks.

----------------------------------------------------------------
The following changes since commit 2166e5edce9ac1edf3b113d6091ef72fcac2d6c4:

  btrfs: fix space_info bytes_may_use underflow during space cache writeout (2020-05-28 14:01:53 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.8-part2-tag

for you to fetch changes up to 55e20bd12a56e06c38b953177bb162cbbaa96004:

  Revert "btrfs: switch to iomap_dio_rw() for dio" (2020-06-14 01:19:02 +0200)

----------------------------------------------------------------
David Sterba (4):
      Revert "btrfs: split btrfs_direct_IO to read and write part"
      Revert "btrfs: remove BTRFS_INODE_READDIO_NEED_LOCK"
      Revert "fs: remove dio_end_io()"
      Revert "btrfs: switch to iomap_dio_rw() for dio"

 fs/btrfs/Kconfig       |   1 -
 fs/btrfs/btrfs_inode.h |  18 +++
 fs/btrfs/ctree.h       |   4 -
 fs/btrfs/file.c        |  97 +------------
 fs/btrfs/inode.c       | 379 +++++++++++++++++++++++++++++++------------------
 fs/direct-io.c         |  19 +++
 include/linux/fs.h     |   2 +
 7 files changed, 286 insertions(+), 234 deletions(-)

             reply	other threads:[~2020-06-14 11:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-14 11:56 David Sterba [this message]
2020-06-14 16:50 ` [GIT PULL] Btrfs updates for 5.8, part 2 Linus Torvalds
2020-06-15 11:46   ` Christoph Hellwig
2020-06-15 12:57   ` David Sterba
2020-06-15 13:26     ` Christoph Hellwig
2020-06-15 13:40       ` Filipe Manana
2020-06-14 18:55 ` pr-tracker-bot

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=cover.1592135316.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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).