From: Mikulas Patocka <mikulas@twibright.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jan Kara <jack@suse.com>,
Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: remove generic_block_fiemap
Date: Tue, 20 Jul 2021 19:02:10 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2107201857100.27763@leontynka> (raw)
In-Reply-To: <20210720133341.405438-1-hch@lst.de>
On Tue, 20 Jul 2021, Christoph Hellwig wrote:
> Hi all,
>
> this series removes the get_block-based generic_block_fiemap helper
> by switching the last two users to use the iomap version instead.
>
> The ext2 version has been tested using xfstests, but the hpfs one
> is only compile tested due to the lack of easy to run tests.
Hi
You can download a test HPFS partition here:
http://artax.karlin.mff.cuni.cz/~mikulas/vyplody/hpfs/test-hpfs-partition.gz
Mikulas
> diffstat:
> fs/ext2/inode.c | 15 +--
> fs/hpfs/file.c | 51 ++++++++++++
> fs/ioctl.c | 203 -------------------------------------------------
> include/linux/fiemap.h | 4
> 4 files changed, 58 insertions(+), 215 deletions(-)
>
next prev parent reply other threads:[~2021-07-20 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 13:33 remove generic_block_fiemap Christoph Hellwig
2021-07-20 13:33 ` [PATCH 1/4] ext2: make ext2_iomap_ops available unconditionally Christoph Hellwig
2021-07-26 13:33 ` Jan Kara
2021-07-20 13:33 ` [PATCH 2/4] ext2: use iomap_fiemap to implement ->fiemap Christoph Hellwig
2021-07-26 13:41 ` Jan Kara
2021-07-20 13:33 ` [PATCH 3/4] hpfs: " Christoph Hellwig
2021-07-20 13:33 ` [PATCH 4/4] fs: remove generic_block_fiemap Christoph Hellwig
2021-07-26 13:52 ` Jan Kara
2021-07-26 13:54 ` Christoph Hellwig
2021-07-26 16:17 ` Jan Kara
2021-07-20 17:02 ` Mikulas Patocka [this message]
2021-07-21 5:37 ` 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=alpine.DEB.2.21.2107201857100.27763@leontynka \
--to=mikulas@twibright.com \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
/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