[PATCH v2 0/2] Avoid setting folio->private

[Goldwyn Rodrigues <rgoldwyn@suse.de>]

From: Goldwyn Rodrigues <rgoldwyn@suse.com>

folio->private was set in order to get release_folio() callbacks.
Instead if we set address_space flags AS_RELEASE_ALWAYS, there is no
need to set EXTENT_FOLIO_PRIVATE on every folio->private.

These patches are posted so we don't face conflicts with iomap's
iomap_folio_state, which also resides in folio->private.

Changes since v1:
 - Incorporated Dave Sterba's comments

Goldwyn Rodrigues (2):
  btrfs: add mapping_set_release_always to inode's mapping
  btrfs: kill EXTENT_FOLIO_PRIVATE

 fs/btrfs/compression.c      |  2 +-
 fs/btrfs/defrag.c           |  2 +-
 fs/btrfs/extent_io.c        | 61 ++++++-------------------------------
 fs/btrfs/extent_io.h        | 10 ++----
 fs/btrfs/file.c             |  6 ++--
 fs/btrfs/free-space-cache.c |  9 ------
 fs/btrfs/inode.c            | 13 +++++---
 fs/btrfs/reflink.c          |  2 +-
 fs/btrfs/relocation.c       |  4 +--
 9 files changed, 27 insertions(+), 82 deletions(-)

-- 
2.48.1