From: Greg KH <greg@kroah.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: stable@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 4.19 0/4] fscrypt: prevent creating duplicate encrypted filenames
Date: Wed, 30 Dec 2020 16:42:15 +0100 [thread overview]
Message-ID: <X+yf12YbaUciBwwf@kroah.com> (raw)
In-Reply-To: <20201228191211.138300-1-ebiggers@kernel.org>
On Mon, Dec 28, 2020 at 11:12:07AM -0800, Eric Biggers wrote:
> Backport four commits from v5.11-rc1. I resolved conflicts in the first
> two.
>
> Eric Biggers (4):
> fscrypt: add fscrypt_is_nokey_name()
> ext4: prevent creating duplicate encrypted filenames
> f2fs: prevent creating duplicate encrypted filenames
> ubifs: prevent creating duplicate encrypted filenames
>
> fs/crypto/hooks.c | 10 +++++-----
> fs/ext4/namei.c | 3 +++
> fs/f2fs/f2fs.h | 2 ++
> fs/ubifs/dir.c | 17 +++++++++++++----
> include/linux/fscrypt_notsupp.h | 5 +++++
> include/linux/fscrypt_supp.h | 29 +++++++++++++++++++++++++++++
> 6 files changed, 57 insertions(+), 9 deletions(-)
>
> --
> 2.29.2
>
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2020-12-30 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 19:12 [PATCH 4.19 0/4] fscrypt: prevent creating duplicate encrypted filenames Eric Biggers
2020-12-28 19:12 ` [PATCH 4.19 1/4] fscrypt: add fscrypt_is_nokey_name() Eric Biggers
2020-12-28 19:12 ` [PATCH 4.19 2/4] ext4: prevent creating duplicate encrypted filenames Eric Biggers
2020-12-28 19:12 ` [PATCH 4.19 3/4] f2fs: " Eric Biggers
2020-12-28 19:12 ` [PATCH 4.19 4/4] ubifs: " Eric Biggers
2020-12-30 15:42 ` Greg KH [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=X+yf12YbaUciBwwf@kroah.com \
--to=greg@kroah.com \
--cc=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=stable@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