[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200901161944.GC669796@gmail.com>
Date: Tue, 1 Sep 2020 09:19:44 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: "Theodore Y. Ts'o" <tytso@....edu>
Cc: linux-ext4@...r.kernel.org, linux-fscrypt@...r.kernel.org
Subject: Re: [PATCH 0/4] e2fsprogs: fix and document the stable_inodes feature
On Mon, Jul 27, 2020 at 09:45:55AM -0700, Eric Biggers wrote:
> On Mon, Jun 15, 2020 at 03:22:40PM -0700, Eric Biggers wrote:
> > On Thu, May 07, 2020 at 11:18:47AM -0700, Eric Biggers wrote:
> > > On Fri, Apr 10, 2020 at 11:24:06AM -0400, Theodore Y. Ts'o wrote:
> > > > On Wed, Apr 01, 2020 at 01:32:35PM -0700, Eric Biggers wrote:
> > > > > Fix tune2fs to not allow cases where IV_INO_LBLK_64-encrypted files
> > > > > (which can exist if the stable_inodes feature is set) could be broken:
> > > > >
> > > > > - Changing the filesystem's UUID
> > > > > - Clearing the stable_inodes feature
> > > > >
> > > > > Also document the stable_inodes feature in the appropriate places.
> > > > >
> > > > > Eric Biggers (4):
> > > > > tune2fs: prevent changing UUID of fs with stable_inodes feature
> > > > > tune2fs: prevent stable_inodes feature from being cleared
> > > > > ext4.5: document the stable_inodes feature
> > > > > tune2fs.8: document the stable_inodes feature
> > > >
> > > > Thanks, I've applied this patch series.
> > > >
> > >
> > > Ted, I still don't see this in git. Are you planning to push it out?
>
> Ping?
Ping.
Powered by blists - more mailing lists