From: Christoph Hellwig <hch@lst.de>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: Christoph Hellwig <hch@lst.de>,
linux-ext4@vger.kernel.org, viro@zeniv.linux.org.uk,
jack@suse.cz, adilger@dilger.ca, riteshh@linux.ibm.com,
amir73il@gmail.com, linux-fsdevel@vger.kernel.org,
linux-unionfs@vger.kernel.org
Subject: Re: fix fiemap for ext4 bitmap files (+ cleanups) v3
Date: Thu, 7 May 2020 16:59:24 +0200 [thread overview]
Message-ID: <20200507145924.GA28854@lst.de> (raw)
In-Reply-To: <20200507144947.GJ404484@mit.edu>
On Thu, May 07, 2020 at 10:49:47AM -0400, Theodore Y. Ts'o wrote:
> On Thu, May 07, 2020 at 08:24:19AM +0200, Christoph Hellwig wrote:
> > On Tue, May 05, 2020 at 05:43:13PM +0200, Christoph Hellwig wrote:
> > > 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.
> >
> > Folks, I think the first two patches should go into 5.7 to fix the
> > ext4 vs overlay problem. Ted, are you going to pick this up, or Al?
>
> I'll pick up the two fixes, thanks. Which tree are the rest of the
> patches going to go through?
vfs.git would be most logic if Al agrees. OTOH there is a fair amount
of ext4 patches, so if you want to pick the series up I wouldn't mind
either.
next prev parent reply other threads:[~2020-05-07 14:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 15:43 fix fiemap for ext4 bitmap files (+ cleanups) v3 Christoph Hellwig
2020-05-05 15:43 ` [PATCH 01/11] ext4: fix EXT4_MAX_LOGICAL_BLOCK macro Christoph Hellwig
2020-05-05 15:43 ` [PATCH 02/11] ext4: fix fiemap size checks for bitmap files Christoph Hellwig
2020-05-06 9:18 ` Jan Kara
2020-05-05 15:43 ` [PATCH 03/11] ext4: split _ext4_fiemap Christoph Hellwig
2020-05-06 9:22 ` Jan Kara
2020-05-05 15:43 ` [PATCH 04/11] ext4: remove the call to fiemap_check_flags in ext4_fiemap Christoph Hellwig
2020-05-06 9:26 ` Jan Kara
2020-05-05 15:43 ` [PATCH 05/11] fs: mark __generic_block_fiemap static Christoph Hellwig
2020-05-06 9:27 ` Jan Kara
2020-05-05 15:43 ` [PATCH 06/11] fs: move the fiemap definitions out of fs.h Christoph Hellwig
2020-05-05 15:43 ` [PATCH 07/11] iomap: fix the iomap_fiemap prototype Christoph Hellwig
2020-05-05 15:43 ` [PATCH 08/11] fs: move fiemap range validation into the file systems instances Christoph Hellwig
2020-05-05 16:01 ` Darrick J. Wong
2020-05-06 4:16 ` Ritesh Harjani
2020-05-05 15:43 ` [PATCH 09/11] fs: handle FIEMAP_FLAG_SYNC in fiemap_prep Christoph Hellwig
2020-05-06 4:17 ` Ritesh Harjani
2020-05-05 15:43 ` [PATCH 10/11] fs: remove the access_ok() check in ioctl_fiemap Christoph Hellwig
2020-05-05 15:43 ` [PATCH 11/11] ext4: remove the access_ok() check in ext4_ioctl_get_es_cache Christoph Hellwig
2020-05-06 9:32 ` Jan Kara
2020-05-07 6:24 ` fix fiemap for ext4 bitmap files (+ cleanups) v3 Christoph Hellwig
2020-05-07 14:49 ` Theodore Y. Ts'o
2020-05-07 14:59 ` Christoph Hellwig [this message]
2020-05-19 8:04 ` Christoph Hellwig
2020-05-20 3:28 ` Theodore Y. Ts'o
2020-05-22 0:00 ` Linus Torvalds
2020-05-22 6:35 ` 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=20200507145924.GA28854@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