stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: akpm@linux-foundation.org, dan.j.williams@intel.com,
	jack@suse.cz, stable@vger.kernel.org,
	torvalds@linux-foundation.org
Subject: Re: FAILED: patch "[PATCH] dax: fix PMD data corruption when fault races with write" failed to apply to 4.10-stable tree
Date: Tue, 23 May 2017 12:25:52 +0200	[thread overview]
Message-ID: <20170523102552.GE28565@kroah.com> (raw)
In-Reply-To: <20170519195412.GA14926@linux.intel.com>

On Fri, May 19, 2017 at 01:54:12PM -0600, Ross Zwisler wrote:
> On Thu, May 18, 2017 at 09:26:31AM +0200, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 4.10-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> > 
> > thanks,
> > 
> > greg k-h
> 
> The patch below is a backport of:
> 
> commit 876f29460cbd ("dax: fix PMD data corruption when fault races with write")
> 
> to v4.10.16.  This was patch 5 in the series.
> 
> This patch still needs a backport of the following ext4 commit (which was
> patch 3 in the series) from Jan to work correctly:
> 
> commit fb26a1cbed8c ("ext4: return to starting transaction in ext4_dax_huge_fault()")

Thanks for this, but 4.10 is now end-of-life, so I'm not going to worry
about the ext4 patch :)

greg k-h

      reply	other threads:[~2017-05-23 10:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18  7:26 FAILED: patch "[PATCH] dax: fix PMD data corruption when fault races with write" failed to apply to 4.10-stable tree gregkh
2017-05-19 19:54 ` Ross Zwisler
2017-05-23 10:25   ` 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=20170523102552.GE28565@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=jack@suse.cz \
    --cc=ross.zwisler@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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).