From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: stable@vger.kernel.org, Eric Biggers <ebiggers@google.com>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH] fscrypto: lock inode while setting encryption policy
Date: Mon, 20 Mar 2017 11:08:07 +0100 [thread overview]
Message-ID: <20170320100807.GA17798@kroah.com> (raw)
In-Reply-To: <20170316222229.3285-1-ebiggers3@gmail.com>
On Thu, Mar 16, 2017 at 03:22:29PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> commit 8906a8223ad4909b391c5628f7991ebceda30e52 upstream. Please apply
> to 4.4-stable; it is already in 4.9-stable. This is a backport of the
> fix to fs/ext4/ and fs/f2fs/ for old kernels.
Thanks, now applied.
greg k-h
next prev parent reply other threads:[~2017-03-20 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 22:22 [PATCH] fscrypto: lock inode while setting encryption policy Eric Biggers
2017-03-20 10:08 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-28 18:34 Eric Biggers
2016-09-29 17:20 ` Richard Weinberger
2016-10-14 18:11 ` Eric Biggers
2016-10-14 18:11 ` Eric Biggers
2016-10-15 13:54 ` Theodore Ts'o
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=20170320100807.GA17798@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--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.