From: Carlos Maiolino <cmaiolino@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: hch@lst.de, adilger@dilger.ca, darrick.wong@oracle.com,
linux-xfs@vger.kernel.org
Subject: [PATCH 0/9 V6] New ->fiemap infrastructure and ->bmap removal
Date: Wed, 11 Sep 2019 15:43:06 +0200 [thread overview]
Message-ID: <20190911134315.27380-1-cmaiolino@redhat.com> (raw)
Hi.
This is the 6th version of the complete series with the goal to deprecate and
eventually remove ->bmap() interface, in lieu if FIEMAP.
This V6, compared with the previous one, is rebased agains next-20190904, and
addresses a few issues found by kbuild test robot, and other points discussed in
previous version.
Detailed information are in each patch description, but the biggest change
in this version is the removal of FIEMAP_KERNEL_FIBMAP flag in patch 8, so,
reducing patch's complexity and avoiding any specific filesystem modification.
The impact of such change is further detailed in patch 8.
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/cifs/cifsfs.h | 3 +-
fs/cifs/inode.c | 5 +-
fs/ecryptfs/mmap.c | 16 +++---
fs/ext2/ext2.h | 3 +-
fs/ext2/inode.c | 6 +--
fs/ext4/ext4.h | 6 +--
fs/ext4/extents.c | 18 +++----
fs/ext4/ioctl.c | 8 +--
fs/f2fs/data.c | 21 +++++---
fs/f2fs/f2fs.h | 3 +-
fs/gfs2/inode.c | 5 +-
fs/hpfs/file.c | 4 +-
fs/inode.c | 108 +++++++++++++++++++++++++++++++++++-----
fs/ioctl.c | 109 ++++++++++++++++++++++++-----------------
fs/iomap/fiemap.c | 4 +-
fs/jbd2/journal.c | 22 ++++++---
fs/nilfs2/inode.c | 5 +-
fs/nilfs2/nilfs.h | 3 +-
fs/ocfs2/extent_map.c | 6 ++-
fs/ocfs2/extent_map.h | 3 +-
fs/overlayfs/inode.c | 5 +-
fs/xfs/xfs_aops.c | 24 ---------
fs/xfs/xfs_iops.c | 14 ++----
fs/xfs/xfs_trace.h | 1 -
include/linux/fs.h | 38 +++++++++-----
include/linux/iomap.h | 2 +-
mm/page_io.c | 11 +++--
31 files changed, 304 insertions(+), 200 deletions(-)
--
2.20.1
next reply other threads:[~2019-09-11 13:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 13:43 Carlos Maiolino [this message]
2019-09-11 13:43 ` [PATCH 1/9] fs: Enable bmap() function to properly return errors Carlos Maiolino
2019-09-11 13:43 ` [PATCH 2/9] cachefiles: drop direct usage of ->bmap method Carlos Maiolino
2019-09-11 13:43 ` [PATCH 3/9] ecryptfs: drop direct calls to ->bmap Carlos Maiolino
2019-09-11 13:43 ` [PATCH 4/9] fibmap: Use bmap instead of ->bmap method in ioctl_fibmap Carlos Maiolino
2019-09-11 13:43 ` [PATCH 5/9] fs: Move start and length fiemap fields into fiemap_extent_info Carlos Maiolino
2019-09-16 17:42 ` Darrick J. Wong
2019-09-11 13:43 ` [PATCH 6/9] iomap: Remove length and start fields from iomap_fiemap Carlos Maiolino
2019-09-11 13:43 ` [PATCH 7/9] fiemap: Use a callback to fill fiemap extents Carlos Maiolino
2019-09-11 13:43 ` [PATCH 8/9] Use FIEMAP for FIBMAP calls Carlos Maiolino
2019-09-16 17:44 ` Darrick J. Wong
2019-09-11 13:43 ` [PATCH 9/9] xfs: Get rid of ->bmap Carlos Maiolino
2019-09-16 17:50 ` Darrick J. Wong
2019-09-18 8:13 ` Carlos Maiolino
2019-09-18 13:24 ` Christoph Hellwig
2019-09-18 16:12 ` Darrick J. Wong
2019-09-23 8:52 ` Carlos Maiolino
2019-09-27 8:59 ` [PATCH 0/9 V6] New ->fiemap infrastructure and ->bmap removal Carlos Maiolino
2019-09-30 8:10 ` Christoph Hellwig
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=20190911134315.27380-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 \
--cc=linux-xfs@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).