From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-ext4@vger.kernel.org, linux-fscrypt@vger.kernel.org,
Satya Tangirala <satyat@google.com>,
Paul Crowley <paulcrowley@google.com>,
Paul Lawrence <paullawrence@google.com>,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [e2fsprogs PATCH] Support the stable_inodes feature
Date: Thu, 31 Oct 2019 19:41:54 -0400 [thread overview]
Message-ID: <20191031234154.GI16197@mit.edu> (raw)
In-Reply-To: <20191021233043.36225-1-ebiggers@kernel.org>
On Mon, Oct 21, 2019 at 04:30:43PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Reserve the codepoint for EXT4_FEATURE_COMPAT_STABLE_INODES, allow it to
> be set and cleared, and teach resize2fs to forbid shrinking the
> filesystem if it is set.
>
> This feature will allow the use of encryption policies where the inode
> number is included in the IVs (initialization vectors) for encryption,
> so data would be corrupted if the inodes were to be renumbered.
>
> For more details, see the kernel patchset:
> https://lkml.kernel.org/linux-fsdevel/20191021230355.23136-1-ebiggers@kernel.org/T/#u
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Thanks, I've applied this as an AOSP cherry-pick. (I've also
synchronized the upstream e2fsprogs git repo with the AOSP e2fsprogs
repo as of 43f6f573dd61 and updated go/aosp-e2fsprogs-reconciliation.
This commit is on the master branch, although the other AOSP commits,
being bug fixes, were landed first on the maint branch and then merged
into master.)
- Ted
prev parent reply other threads:[~2019-10-31 23:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 23:30 [e2fsprogs PATCH] Support the stable_inodes feature Eric Biggers
2019-10-31 23:41 ` Theodore Y. Ts'o [this message]
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=20191031234154.GI16197@mit.edu \
--to=tytso@mit.edu \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=paulcrowley@google.com \
--cc=paullawrence@google.com \
--cc=satyat@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.