From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: stable@vger.kernel.org, Richard Weinberger <richard@nod.at>,
Theodore Ts'o <tytso@mit.edu>, Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH] ext4: require encryption feature for EXT4_IOC_SET_ENCRYPTION_POLICY
Date: Fri, 5 May 2017 10:57:44 -0700 [thread overview]
Message-ID: <20170505175744.GA12923@kroah.com> (raw)
In-Reply-To: <20170502211532.33611-1-ebiggers3@gmail.com>
On Tue, May 02, 2017 at 02:15:32PM -0700, Eric Biggers wrote:
> From: Richard Weinberger <richard@nod.at>
>
> commit 9a200d075e5d05be1fcad4547a0f8aee4e2f9a04 upstream. Please apply
> to 4.4-stable. (Having to make this change is unfortunate since it
> could break some users of ext4 encryption, but we haven't received any
> complaints about this being in the 4.9 kernel, and we need to do this
> because otherwise anyone who can write to an ext4 filesystem with
> block_size != PAGE_SIZE can crash the kernel or corrupt the filesystem.)
>
> ...otherwise an user can enable encryption for certain files even
> when the filesystem is unable to support it.
> Such a case would be a filesystem created by mkfs.ext4's default
> settings, 1KiB block size. Ext4 supports encyption only when block size
> is equal to PAGE_SIZE.
> But this constraint is only checked when the encryption feature flag
> is set.
>
> Signed-off-by: Richard Weinberger <richard@nod.at>
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> fs/ext4/ioctl.c | 3 +++
> 1 file changed, 3 insertions(+)
This was for 4.4, right? Now queued up there.
greg k-h
prev parent reply other threads:[~2017-05-05 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 21:15 [PATCH] ext4: require encryption feature for EXT4_IOC_SET_ENCRYPTION_POLICY Eric Biggers
2017-05-05 17:57 ` Greg Kroah-Hartman [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=20170505175744.GA12923@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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.