From: "Williams, Dan J" <dan.j.williams@intel.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: [GIT PULL] dax fixes for 4.19-rc8
Date: Sat, 13 Oct 2018 17:25:21 +0000 [thread overview]
Message-ID: <8f47e3ce3cbe6e165701dbf665bb1770ca13d907.camel@intel.com> (raw)
Hi Greg, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-fixes-4.19-rc8
...to receive (2) urgent dax fixes for 4.19-rc8. They have appeared in
a -next release.
However, note that commit d7782145e1ad ("filesystem-dax: Fix
dax_layout_busy_page() livelock") is immediately replaced with the
Xarray conversion targeting 4.20, so d7782145e1ad is the backport
suitable fix for the livelock for v4.19 and earlier.
Please pull, thanks!
---
The following changes since commit 17b57b1883c1285f3d0dc2266e8f79286a7bef38:
Linux 4.19-rc6 (2018-09-30 07:15:35 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-fixes-4.19-rc8
for you to fetch changes up to 4628a64591e6cee181237060961e98c615c33966:
mm: Preserve _PAGE_DEVMAP across mprotect() calls (2018-10-09 11:44:58 -0700)
----------------------------------------------------------------
libnvdimm/dax 4.19-rc8
* Fix a livelock in dax_layout_busy_page() present since v4.18. The
lockup triggers when truncating an actively mapped huge page out of a
mapping pinned for direct-I/O.
* Fix mprotect() clobbers of _PAGE_DEVMAP. Broken since v4.5 mprotect()
clears this flag that is needed to communicate the liveness of device
pages to the get_user_pages() path.
----------------------------------------------------------------
Dan Williams (1):
filesystem-dax: Fix dax_layout_busy_page() livelock
Jan Kara (1):
mm: Preserve _PAGE_DEVMAP across mprotect() calls
arch/powerpc/include/asm/book3s/64/pgtable.h | 4 ++--
arch/x86/include/asm/pgtable_types.h | 2 +-
fs/dax.c | 13 +++++++++++--
3 files changed, 14 insertions(+), 5 deletions(-)
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next reply other threads:[~2018-10-13 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 17:25 Williams, Dan J [this message]
2018-10-14 6:55 ` [GIT PULL] dax fixes for 4.19-rc8 gregkh
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=8f47e3ce3cbe6e165701dbf665bb1770ca13d907.camel@intel.com \
--to=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.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