From: Greg KH <greg@kroah.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: stable@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
David Howells <dhowells@redhat.com>,
Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH 1/3] f2fs crypto: replace some BUG_ON()'s with error checks
Date: Wed, 25 Oct 2017 11:39:46 +0200 [thread overview]
Message-ID: <20171025093946.GB25651@kroah.com> (raw)
In-Reply-To: <20171024193003.58499-1-ebiggers3@gmail.com>
On Tue, Oct 24, 2017 at 12:30:01PM -0700, Eric Biggers wrote:
> From: Jaegeuk Kim <jaegeuk@kernel.org>
>
> commit 66aa3e1274fcf887e9d6501a68163270fc7718e7 upstream. Please apply
> to 4.4-stable.
Thanks for all 3 of these patches, now queued up.
greg k-h
prev parent reply other threads:[~2017-10-25 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 19:30 [PATCH 1/3] f2fs crypto: replace some BUG_ON()'s with error checks Eric Biggers
2017-10-24 19:30 ` [PATCH 2/3] f2fs crypto: add missing locking for keyring_key access Eric Biggers
2017-10-24 19:30 ` [PATCH 3/3] fscrypt: fix dereference of NULL user_key_payload Eric Biggers
2017-10-25 9:39 ` 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=20171025093946.GB25651@kroah.com \
--to=greg@kroah.com \
--cc=dhowells@redhat.com \
--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).