All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "George G. Davis" <george_davis@mentor.com>
Cc: stable@vger.kernel.org, Dirk Behme <dirk.behme@de.bosch.com>,
	Jan Kara <jack@suse.cz>, Theodore Ts'o <tytso@mit.edu>,
	weller huang <weller.huang@cn.bosch.com>
Subject: Re: [PATCH 3.14] ext4: fix data exposure after a crash
Date: Sun, 14 Aug 2016 16:50:54 +0200	[thread overview]
Message-ID: <20160814145054.GD27230@kroah.com> (raw)
In-Reply-To: <1467153108-104061-1-git-send-email-george_davis@mentor.com>

On Tue, Jun 28, 2016 at 06:31:48PM -0400, George G. Davis wrote:
> From: Jan Kara <jack@suse.cz>
> 
> From: Jan Kara <jack@suse.cz>
> 
> commit 06bd3c36a733ac27962fea7d6f47168841376824 upstream

What about a 4.4-stable version of this?  I don't want to take this into
3.14-stable without that.

thanks,

greg k-h

      parent reply	other threads:[~2016-08-14 14:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-04 21:46 FAILED: patch "[PATCH] ext4: fix data exposure after a crash" failed to apply to 3.14-stable tree gregkh
2016-06-06  0:02 ` HUANG Weller (CM/ESW12-CN)
2016-06-06  0:02   ` HUANG Weller (CM/ESW12-CN)
2016-06-06  5:16   ` Arend van Spriel
2016-06-06  6:17     ` HUANG Weller (CM/ESW12-CN)
2016-06-06  6:17       ` HUANG Weller (CM/ESW12-CN)
2016-06-28 22:31 ` [PATCH 3.14] ext4: fix data exposure after a crash George G. Davis
2016-06-29  7:46   ` Jan Kara
2017-10-06 10:04     ` HUANG Weller (CM/ESW12-CN)
2017-10-09 11:05       ` Jan Kara
2017-10-09 13:20         ` Ext4 support for LTS kernels (was: Re: [PATCH 3.14] ext4: fix data exposure after a crash) Theodore Ts'o
2017-10-10 18:17           ` Greg KH
2017-10-19 11:35             ` Greg KH
2016-08-14 14:50   ` 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=20160814145054.GD27230@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dirk.behme@de.bosch.com \
    --cc=george_davis@mentor.com \
    --cc=jack@suse.cz \
    --cc=stable@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=weller.huang@cn.bosch.com \
    /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.