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 5.4 0/4] fscrypt: prevent creating duplicate encrypted filenames
Date: Wed, 30 Dec 2020 16:39:24 +0100 [thread overview]
Message-ID: <X+yfLAyAw8kOcOGz@kroah.com> (raw)
In-Reply-To: <20201228185433.61129-1-ebiggers@kernel.org>
On Mon, Dec 28, 2020 at 10:54:29AM -0800, Eric Biggers wrote:
> Backport four commits from v5.11-rc1. I resolved a conflict in the
> first one. The rest are clean cherry-picks which didn't get picked up
> yet because they depend on the first one.
>
> 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
>
All now applied, thanks.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-mtd@lists.infradead.org, stable@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 5.4 0/4] fscrypt: prevent creating duplicate encrypted filenames
Date: Wed, 30 Dec 2020 16:39:24 +0100 [thread overview]
Message-ID: <X+yfLAyAw8kOcOGz@kroah.com> (raw)
In-Reply-To: <20201228185433.61129-1-ebiggers@kernel.org>
On Mon, Dec 28, 2020 at 10:54:29AM -0800, Eric Biggers wrote:
> Backport four commits from v5.11-rc1. I resolved a conflict in the
> first one. The rest are clean cherry-picks which didn't get picked up
> yet because they depend on the first one.
>
> 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
>
All now applied, thanks.
greg k-h
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-mtd@lists.infradead.org, stable@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 5.4 0/4] fscrypt: prevent creating duplicate encrypted filenames
Date: Wed, 30 Dec 2020 16:39:24 +0100 [thread overview]
Message-ID: <X+yfLAyAw8kOcOGz@kroah.com> (raw)
In-Reply-To: <20201228185433.61129-1-ebiggers@kernel.org>
On Mon, Dec 28, 2020 at 10:54:29AM -0800, Eric Biggers wrote:
> Backport four commits from v5.11-rc1. I resolved a conflict in the
> first one. The rest are clean cherry-picks which didn't get picked up
> yet because they depend on the first one.
>
> 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
>
All now applied, thanks.
greg k-h
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-12-30 15:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 18:54 [PATCH 5.4 0/4] fscrypt: prevent creating duplicate encrypted filenames Eric Biggers
2020-12-28 18:54 ` Eric Biggers
2020-12-28 18:54 ` [f2fs-dev] " Eric Biggers
2020-12-28 18:54 ` [PATCH 5.4 1/4] fscrypt: add fscrypt_is_nokey_name() Eric Biggers
2020-12-28 18:54 ` Eric Biggers
2020-12-28 18:54 ` [f2fs-dev] " Eric Biggers
2020-12-30 15:39 ` [f2fs-dev] Patch "fscrypt: add fscrypt_is_nokey_name()" has been added to the 5.4-stable tree gregkh
2020-12-30 15:39 ` gregkh
2020-12-28 18:54 ` [PATCH 5.4 2/4] ext4: prevent creating duplicate encrypted filenames Eric Biggers
2020-12-28 18:54 ` Eric Biggers
2020-12-28 18:54 ` [f2fs-dev] " Eric Biggers
2020-12-30 15:39 ` [f2fs-dev] Patch "ext4: prevent creating duplicate encrypted filenames" has been added to the 5.4-stable tree gregkh
2020-12-30 15:39 ` gregkh
2020-12-28 18:54 ` [PATCH 5.4 3/4] f2fs: prevent creating duplicate encrypted filenames Eric Biggers
2020-12-28 18:54 ` Eric Biggers
2020-12-28 18:54 ` [f2fs-dev] " Eric Biggers
2020-12-30 15:39 ` [f2fs-dev] Patch "f2fs: prevent creating duplicate encrypted filenames" has been added to the 5.4-stable tree gregkh
2020-12-30 15:39 ` gregkh
2020-12-28 18:54 ` [PATCH 5.4 4/4] ubifs: prevent creating duplicate encrypted filenames Eric Biggers
2020-12-28 18:54 ` Eric Biggers
2020-12-28 18:54 ` [f2fs-dev] " Eric Biggers
2020-12-30 15:39 ` [f2fs-dev] Patch "ubifs: prevent creating duplicate encrypted filenames" has been added to the 5.4-stable tree gregkh
2020-12-30 15:39 ` gregkh
2020-12-30 15:39 ` Greg KH [this message]
2020-12-30 15:39 ` [PATCH 5.4 0/4] fscrypt: prevent creating duplicate encrypted filenames Greg KH
2020-12-30 15:39 ` [f2fs-dev] " Greg KH
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+yfLAyAw8kOcOGz@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 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.