From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: stable@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
Eric Biggers <ebiggers@google.com>, Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH 1/2] f2fs: check entire encrypted bigname when finding a dentry
Date: Tue, 23 May 2017 12:22:28 +0200 [thread overview]
Message-ID: <20170523102228.GC28565@kroah.com> (raw)
In-Reply-To: <20170518180711.22969-1-ebiggers3@gmail.com>
On Thu, May 18, 2017 at 11:07:10AM -0700, Eric Biggers wrote:
> From: Jaegeuk Kim <jaegeuk@kernel.org>
>
> commit 6332cd32c8290a80e929fc044dc5bdba77396e33 upstream. Please apply
> to 4.9-stable.
Thanks for all of these backports, now queued up.
greg k-h
next prev parent reply other threads:[~2017-05-23 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 18:07 [PATCH 1/2] f2fs: check entire encrypted bigname when finding a dentry Eric Biggers
2017-05-18 18:07 ` [PATCH 2/2] fscrypt: avoid collisions when presenting long encrypted filenames Eric Biggers
2017-05-23 10:22 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-18 18:19 [PATCH 1/2] f2fs: check entire encrypted bigname when finding a dentry Eric Biggers
2017-05-18 18:01 Eric Biggers
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=20170523102228.GC28565@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--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 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 NNTP newsgroup(s).