Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 15 Jun 2020 15:22:40 -0700
From:   Eric Biggers <ebiggers@kernel.org>
To:     "Theodore Y. Ts'o" <tytso@mit.edu>
Cc:     linux-ext4@vger.kernel.org, linux-fscrypt@vger.kernel.org
Subject: Re: [PATCH 0/4] e2fsprogs: fix and document the stable_inodes feature
Message-ID: <20200615222240.GD85413@gmail.com>
References: <20200401203239.163679-1-ebiggers@kernel.org>
 <20200410152406.GO45598@mit.edu>
 <20200507181847.GD236103@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200507181847.GD236103@gmail.com>
Sender: linux-ext4-owner@vger.kernel.org
Precedence: bulk

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?