From: "Theodore Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers@kernel.org>, linux-ext4@vger.kernel.org
Cc: "Theodore Ts'o" <tytso@mit.edu>, linux-fscrypt@vger.kernel.org
Subject: Re: [e2fsprogs PATCH v2] e2fsck: don't allow journal inode to have encrypt flag
Date: Thu, 19 Jan 2023 10:27:05 -0500 [thread overview]
Message-ID: <167414201626.2737146.9945075617467030108.b4-ty@mit.edu> (raw)
In-Reply-To: <20221102220551.3940-1-ebiggers@kernel.org>
On Wed, 2 Nov 2022 15:05:51 -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Since the kernel is being fixed to consider journal inodes with the
> 'encrypt' flag set to be invalid, also update e2fsck accordingly.
>
>
Applied, thanks!
[1/1] e2fsck: don't allow journal inode to have encrypt flag
commit: b0cd09e5b65373fc9f89048958c093bb1e6a1ecb
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
prev parent reply other threads:[~2023-01-19 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 22:05 [e2fsprogs PATCH v2] e2fsck: don't allow journal inode to have encrypt flag Eric Biggers
2022-11-02 22:48 ` Andreas Dilger
2023-01-09 18:20 ` Eric Biggers
2023-01-19 15:27 ` Theodore 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=167414201626.2737146.9945075617467030108.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).