From: Sasha Levin <sashal@kernel.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Greg KH <gregkh@linuxfoundation.org>, Jan Kara <jack@suse.cz>,
stable <stable@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: FAILED: patch "[PATCH] dax: Don't access a freed inode" failed to apply to 4.19-stable tree
Date: Sat, 22 Dec 2018 14:04:47 -0500 [thread overview]
Message-ID: <20181222190447.GO86645@sasha-vm> (raw)
In-Reply-To: <CAPcyv4hHnR95zAcxU9RqZvbaP1BB0_NUFsRuQcDY9zkKKQV_Ug@mail.gmail.com>
On Fri, Dec 21, 2018 at 12:31:02PM -0800, Dan Williams wrote:
>On Thu, Dec 13, 2018 at 11:14 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>>
>> On Tue, Dec 11, 2018 at 07:23:49AM -0800, Matthew Wilcox wrote:
>> > On Tue, Dec 11, 2018 at 03:00:09PM +0100, gregkh@linuxfoundation.org wrote:
>> > >
>> > > The patch below does not apply to the 4.19-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>.
>> >
>> > I have only compile-tested this backport. Dan, do you want to run it
>> > through some tests before Greg applies it?
>>
>> Thanks for the backport, I'll wait to hear from Dan before queueing this
>> up.
>
>Tested-by: Dan Williams <dan.j.williams@intel.com>
>
>However, on the upstream version of this fix Linus pointed out an
>additional fixup. Once that goes upstream [1] I'll circle back to
>provide a fixed up version of this backport to keep -stable and
>mainline more aligned.
>
>[1]: https://marc.info/?l=linux-fsdevel&m=154542184202064&w=2
Okay, I guess it makes sense to wait for the fixup before we pull this
backport in?
--
Thanks,
Sasha
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-12-22 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1544536809243247@kroah.com>
2018-12-11 15:23 ` FAILED: patch "[PATCH] dax: Don't access a freed inode" failed to apply to 4.19-stable tree Matthew Wilcox
2018-12-14 7:13 ` Greg KH
2018-12-21 20:31 ` Dan Williams
2018-12-22 19:04 ` Sasha Levin [this message]
2018-12-22 19:33 ` Dan Williams
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=20181222190447.GO86645@sasha-vm \
--to=sashal@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-nvdimm@lists.01.org \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.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