From: Dan Williams <dan.j.williams@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] dax fixes v5.3-rc4
Date: Sun, 11 Aug 2019 12:01:02 -0700 [thread overview]
Message-ID: <CAPcyv4iaYiXbv2sf-Znn5dYphLKEi77NjafkEzXA2kAEMqyR0w@mail.gmail.com> (raw)
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/dax-fixes-5.3-rc4
...a filesystem-dax and device-dax fix for v5.3. The filesystem-dax
fix is tagged for stable as the implementation has been mistakenly
throwing away all cow pages on any truncate or hole punch operation as
part of the solution to coordinate device-dma vs truncate to dax
pages. The device-dax change fixes up a regression this cycle from the
introduction of a common 'internal per-cpu-ref' implementation.
The filesystem-dax fix has appeared in -next. The device-dax has not,
but it has been exposed on a kbuild-robot visible branch for the past
few days, and passes the nvdimm unit tests.
---
The following changes since commit e21a712a9685488f5ce80495b37b9fdbe96c230d:
Linux 5.3-rc3 (2019-08-04 18:40:12 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/dax-fixes-5.3-rc4
for you to fetch changes up to 06282373ff57a2b82621be4f84f981e1b0a4eb28:
mm/memremap: Fix reuse of pgmap instances with internal references
(2019-08-09 14:16:15 -0700)
----------------------------------------------------------------
dax fixes v5.3-rc4
- Fix dax_layout_busy_page() to not discard private cow pages of fs/dax
private mappings.
- Update the memremap_pages core to properly cleanup on behalf of
internal reference-count users like device-dax.
----------------------------------------------------------------
Dan Williams (1):
mm/memremap: Fix reuse of pgmap instances with internal references
Vivek Goyal (1):
dax: dax_layout_busy_page() should not unmap cow pages
fs/dax.c | 2 +-
mm/memremap.c | 6 ++++++
2 files changed, 7 insertions(+), 1 deletion(-)
next reply other threads:[~2019-08-11 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 19:01 Dan Williams [this message]
2019-08-11 20:20 ` [GIT PULL] dax fixes v5.3-rc4 pr-tracker-bot
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=CAPcyv4iaYiXbv2sf-Znn5dYphLKEi77NjafkEzXA2kAEMqyR0w@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.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).