linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: linux-ext4@vger.kernel.org, viro@zeniv.linux.org.uk
Cc: jack@suse.cz, tytso@mit.edu, adilger@dilger.ca,
	riteshh@linux.ibm.com, amir73il@gmail.com,
	linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org
Subject: fix fiemap for ext4 bitmap files (+ cleanups)
Date: Mon, 27 Apr 2020 11:58:50 +0200	[thread overview]
Message-ID: <20200427095858.1440608-1-hch@lst.de> (raw)

Hi all,

the first two patches should fix the issue where ext4 doesn't
properly check the max file size for bitmap files in fiemap.

The rest cleans up the fiemap support in ext4 and in general.

             reply	other threads:[~2020-04-27  9:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27  9:58 Christoph Hellwig [this message]
2020-04-27  9:58 ` [PATCH 1/8] ext4: fix EXT4_MAX_LOGICAL_BLOCK macro Christoph Hellwig
2020-04-27  9:58 ` [PATCH 2/8] ext4: fix fiemap size checks for bitmap files Christoph Hellwig
2020-04-27  9:58 ` [PATCH 3/8] ext4: split _ext4_fiemap Christoph Hellwig
2020-04-27  9:58 ` [PATCH 4/8] ext4: remove the call to fiemap_check_flags in ext4_fiemap Christoph Hellwig
2020-04-27  9:58 ` [PATCH 5/8] fs: mark __generic_block_fiemap static Christoph Hellwig
2020-04-27  9:58 ` [PATCH 6/8] fs: move the fiemap definitions out of fs.h Christoph Hellwig
2020-04-27  9:58 ` [PATCH 7/8] iomap: fix the iomap_fiemap prototype Christoph Hellwig
2020-04-27  9:58 ` [PATCH 8/8] fs: move fiemap range validation into the file systems instances 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=20200427095858.1440608-1-hch@lst.de \
    --to=hch@lst.de \
    --cc=adilger@dilger.ca \
    --cc=amir73il@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=riteshh@linux.ibm.com \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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).