From: Sasha Levin <sashal@kernel.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: stable@vger.kernel.org, Matthew Wilcox <willy@infradead.org>,
Jan Kara <jack@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [4.19-stable PATCH 0/2] dax: Don't access a freed inode
Date: Sun, 6 Jan 2019 12:45:11 -0500 [thread overview]
Message-ID: <20190106174511.GD166797@sasha-vm> (raw)
In-Reply-To: <154671750268.249397.710993904552440547.stgit@dwillia2-desk3.amr.corp.intel.com>
On Sat, Jan 05, 2019 at 11:45:02AM -0800, Dan Williams wrote:
>The original upstream fix, commit 55e56f06ed71 "dax: Don't access a freed
>inode", prompted an immediate cleanup request. Now that the cleanup has
>landed, commit d8a706414af4 "dax: Use non-exclusive wait in
>wait_entry_unlocked()", backport them both to -stable.
Queued for 4.19, thank you.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-01-06 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 19:45 Dan Williams
2019-01-05 19:45 ` [4.19-stable PATCH 1/2] " Dan Williams
2019-01-05 19:45 ` [4.19-stable PATCH 2/2] dax: Use non-exclusive wait in wait_entry_unlocked() Dan Williams
2019-01-06 17:45 ` Sasha Levin [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=20190106174511.GD166797@sasha-vm \
--to=sashal@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome