From: Carlos Maiolino <cmaiolino@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: hch@lst.de, darrick.wong@oracle.com, adilger@dilger.ca
Subject: [PATCH 0/9 V3] New ->fiemap infrastructure and ->bmap removal
Date: Mon, 18 Feb 2019 14:03:22 +0100 [thread overview]
Message-ID: <20190218130331.15882-1-cmaiolino@redhat.com> (raw)
Hi.
This is the 3rd version of the complete series with the goal to remove ->bmap
interface completely, in lieu of FIEMAP.
This new version has been slightly modified in comparison with the second one,
based on reviews of the second version. My apologies if I forgot to update
anything based on previous discussion.
Patch 1-3 have no difference from the previous version, and Christoph's
Reviewed-by has been kept.
Patch 4 is a V3 of the previous set, Containing just a small update renaming a
variable.
Patches 5-6 are the same from previous version, including now Christoph's
Reviewed-by tahg.
Patch 7 contains a merge of patches 7 and 8 from the previous version, a small
conflict fix when rebasing on top of linux-next, and a rename of the pointer
holding the fiemap callback.
Patch 8 is the biggest change in this patchset, and has been flagged as a RFC
giving the fact we have not reached a decision on how the replacement of ->bmap
by ->fiemap should be done. The patch description has all details.
Patch 9 is a V2 from the previous patchset, including removal of iomap unused
functions.
As always, comments are much appreciated.
Cheers
Carlos Maiolino (9):
fs: Enable bmap() function to properly return errors
cachefiles: drop direct usage of ->bmap method.
ecryptfs: drop direct calls to ->bmap
fibmap: Use bmap instead of ->bmap method in ioctl_fibmap
fs: Move start and length fiemap fields into fiemap_extent_info
iomap: Remove length and start fields from iomap_fiemap
fiemap: Use a callback to fill fiemap extents
Use FIEMAP for FIBMAP calls
xfs: Get rid of ->bmap
drivers/md/md-bitmap.c | 16 ++++--
fs/bad_inode.c | 3 +-
fs/btrfs/inode.c | 5 +-
fs/cachefiles/rdwr.c | 27 ++++-----
fs/ecryptfs/mmap.c | 16 ++----
fs/ext2/ext2.h | 3 +-
fs/ext2/inode.c | 6 +-
fs/ext4/ext4.h | 3 +-
fs/ext4/extents.c | 15 +++--
fs/f2fs/data.c | 10 +++-
fs/f2fs/f2fs.h | 3 +-
fs/gfs2/inode.c | 5 +-
fs/hpfs/file.c | 4 +-
fs/inode.c | 106 +++++++++++++++++++++++++++++-----
fs/ioctl.c | 126 ++++++++++++++++++++++++++---------------
fs/iomap.c | 40 ++-----------
fs/jbd2/journal.c | 22 ++++---
fs/nilfs2/inode.c | 5 +-
fs/nilfs2/nilfs.h | 3 +-
fs/ocfs2/extent_map.c | 13 ++++-
fs/ocfs2/extent_map.h | 3 +-
fs/overlayfs/inode.c | 5 +-
fs/xfs/xfs_aops.c | 24 --------
fs/xfs/xfs_iops.c | 19 ++++---
fs/xfs/xfs_trace.h | 1 -
include/linux/fs.h | 33 +++++++----
include/linux/iomap.h | 2 +-
mm/page_io.c | 11 ++--
28 files changed, 309 insertions(+), 220 deletions(-)
--
2.17.2
next reply other threads:[~2019-02-18 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 13:03 Carlos Maiolino [this message]
2019-02-18 13:03 ` [PATCH 1/9] fs: Enable bmap() function to properly return errors Carlos Maiolino
2019-02-18 13:03 ` [PATCH 2/9] cachefiles: drop direct usage of ->bmap method Carlos Maiolino
2019-02-18 13:03 ` [PATCH 3/9] ecryptfs: drop direct calls to ->bmap Carlos Maiolino
2019-02-18 13:03 ` [PATCH 4/9 V3] fibmap: Use bmap instead of ->bmap method in ioctl_fibmap Carlos Maiolino
2019-02-18 13:03 ` [PATCH 5/9] fs: Move start and length fiemap fields into fiemap_extent_info Carlos Maiolino
2019-02-18 13:03 ` [PATCH 6/9] iomap: Remove length and start fields from iomap_fiemap Carlos Maiolino
2019-02-18 13:03 ` [PATCH 7/9 V3] fiemap: Use a callback to fill fiemap extents Carlos Maiolino
2019-02-18 13:03 ` [PATCH RFC 8/9] Use FIEMAP for FIBMAP calls Carlos Maiolino
2019-02-20 7:01 ` Andreas Dilger
2019-02-20 8:37 ` Carlos Maiolino
2019-02-18 13:03 ` [PATCH 9/9 V2] xfs: Get rid of ->bmap Carlos Maiolino
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=20190218130331.15882-1-cmaiolino@redhat.com \
--to=cmaiolino@redhat.com \
--cc=adilger@dilger.ca \
--cc=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.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).