[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200524191713.GA228632@mit.edu>
Date: Sun, 24 May 2020 15:17:13 -0400
From: "Theodore Y. Ts'o" <tytso@....edu>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Christoph Hellwig <hch@....de>, linux-ext4@...r.kernel.org,
jack@...e.cz, adilger@...ger.ca, riteshh@...ux.ibm.com,
amir73il@...il.com, linux-fsdevel@...r.kernel.org,
linux-unionfs@...r.kernel.org
Subject: Re: fiemap cleanups v4
On Sat, May 23, 2020 at 04:52:16PM +0100, Al Viro wrote:
> On Sat, May 23, 2020 at 09:30:07AM +0200, Christoph Hellwig wrote:
> > Hi all,
> >
> > This series cleans up the fiemap support in ext4 and in general.
> >
> > Ted or Al, can one of you pick this up? It touches both ext4 and core
> > code, so either tree could work.
> >
> >
> > Changes since v3:
> > - dropped the fixes that have been merged int mainline
> >
> > Changes since v2:
> > - commit message typo
> > - doc updates
> > - use d_inode in cifs
> > - add a missing return statement in cifs
> > - remove the filemap_write_and_wait call from ext4_ioctl_get_es_cache
> >
> > Changes since v1:
> > - rename fiemap_validate to fiemap_prep
> > - lift FIEMAP_FLAG_SYNC handling to common code
> > - add a new linux/fiemap.h header
> > - remove __generic_block_fiemap
> > - remove access_ok calls from fiemap and ext4
>
> Hmmm... I can do an immutable shared branch, no problem. What would
> you prefer for a branchpoint for that one?
I thought we had already agreed to run these patches through the ext4
git tree, since most of the changes affect the ext4 tree (and there
aren't any other iomap fiemap changes pending as far as I know).
The v3 versions of these patches have been part of the ext4 dev tree
since May 19th. Since the ext4 dev tree is rewinding, I can easily
update it fiemap-fixes patch to be on top of the first two patches
which Linus has already accepted, and then merge it into the ext4 dev
branch.
- Ted
Powered by blists - more mailing lists