From: Carlos Maiolino <cmaiolino@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: hch@lst.de, darrick.wong@oracle.com, sandeen@sandeen.net
Subject: [PATCH 0/5] Refactor ioctl_fibmap() internal interface
Date: Fri, 22 Nov 2019 09:53:15 +0100 [thread overview]
Message-ID: <20191122085320.124560-1-cmaiolino@redhat.com> (raw)
Hi,
This series refactor the internal structure of FIBMAP so that the filesystem can
properly report errors back to VFS, and also simplifies its usage by
standardizing all ->bmap() method usage via bmap() function.
The last patch is a bug fix for ioctl_fibmap() calls with negative block values.
This patchset is essentially a part of the original series reworking FIEMAP to
also be used for FIBMAP calls.
Due the fact the original series makes too many changes, I decided to split it
into smaller series, so they can be reviewed and applied individually, with
specific purposes, instead of changing everything in a single set. I believe
this makes the review process for this work easier too.
Cheers.
Carlos Maiolino (5):
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
fibmap: Reject negative block numbers
drivers/md/md-bitmap.c | 16 ++++++++++------
fs/cachefiles/rdwr.c | 27 ++++++++++++++-------------
fs/ecryptfs/mmap.c | 16 ++++++----------
fs/f2fs/data.c | 16 +++++++++++-----
fs/inode.c | 30 +++++++++++++++++-------------
fs/ioctl.c | 32 ++++++++++++++++++++++----------
fs/jbd2/journal.c | 22 +++++++++++++++-------
include/linux/fs.h | 9 ++++++++-
mm/page_io.c | 11 +++++++----
9 files changed, 110 insertions(+), 69 deletions(-)
--
2.23.0
next reply other threads:[~2019-11-22 8:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 8:53 Carlos Maiolino [this message]
2019-11-22 8:53 ` [PATCH 1/5] fs: Enable bmap() function to properly return errors Carlos Maiolino
2019-11-22 13:37 ` Christoph Hellwig
2019-11-22 14:02 ` Carlos Maiolino
2019-11-22 14:07 ` Christoph Hellwig
2019-11-22 8:53 ` [PATCH 2/5] cachefiles: drop direct usage of ->bmap method Carlos Maiolino
2019-11-22 13:37 ` Christoph Hellwig
2019-11-22 14:04 ` Carlos Maiolino
2019-11-22 8:53 ` [PATCH 3/5] ecryptfs: drop direct calls to ->bmap Carlos Maiolino
2019-11-22 8:53 ` [PATCH 4/5] fibmap: Use bmap instead of ->bmap method in ioctl_fibmap Carlos Maiolino
2019-11-22 13:38 ` Christoph Hellwig
2019-11-24 9:56 ` kbuild test robot
2019-11-24 14:52 ` kbuild test robot
2019-11-22 8:53 ` [PATCH 5/5] fibmap: Reject negative block numbers Carlos Maiolino
2019-11-22 13:38 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2019-12-10 15:03 [PATCH 0/5] Refactor ioctl_fibmap() internal interface 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=20191122085320.124560-1-cmaiolino@redhat.com \
--to=cmaiolino@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).