public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: John Groves <John@groves.net>, Dan Williams <djbw@kernel.org>,
	"Alison Schofield" <alison.schofield@intel.com>,
	John Groves <jgroves@micron.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Jonathan Cameron <jic23@kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <nvdimm@lists.linux.dev>,
	<linux-cxl@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>
Subject: [GIT PULL] DAX for 7.1
Date: Tue, 21 Apr 2026 14:35:48 -0500	[thread overview]
Message-ID: <69e7d1949ebcc_7d12a10098@iweiny-mobl.notmuch> (raw)

Hi Linus,

Please pull from:

  git@gitolite.kernel.org:pub/scm/linux/kernel/git/nvdimm/nvdimm.git tags/libnvdimm-for-7.1

To get changes for the dax subsystem for 7.1.

This was delayed from last week due to the issue fixed in the last patch.  It
has now soaked in linux-next over the weekend.

The series adds DAX support required for the upcoming fuse/famfs file
system.[1]  The support here is required because famfs is backed by devdax
rather than pmem.  This all lays the groundwork for using shared memory as a
file system.

There have been some late breaking change requests to famfs.  As such it looks
like it will not land in this cycle.  However, this work will be used
regardless of the outcome of the changes being discussed.  Those changes are
well above the code uses between dax and fuse.  Therefore, I'm moving forward
landing this so that the famfs work can proceed less encumbered.

Finally, there was a small merge conflict fixed in linux-next.[2]  The fix
there is correct.

Thanks,
Ira

[1] https://lore.kernel.org/all/0100019d43e5f632-f5862a3e-361c-4b54-a9a6-96c242a8f17a-000000@email.amazonses.com/
[2] https://lore.kernel.org/all/ac0bwb8BPmZ1_aoT@sirena.org.uk/

---

The following changes since commit 7aaa8047eafd0bd628065b15757d9b48c5f9c07d:

  Linux 7.0-rc6 (2026-03-29 15:40:00 -0700)

are available in the Git repository at:

  git@gitolite.kernel.org:pub/scm/linux/kernel/git/nvdimm/nvdimm.git tags/libnvdimm-for-7.1

for you to fetch changes up to 45df9111692c62d5f09fc4345ae36dae31024797:

  dax/fsdev: fix uninitialized kaddr in fsdev_dax_zero_page_range() (2026-04-13 14:15:15 -0500)

----------------------------------------------------------------
dax changes for 7.1

The new FUSE file system requires some DAX changes.

	* dax/fsdev: fix uninitialized kaddr in fsdev_dax_zero_page_range()
	* dax: export dax_dev_get()
	* dax: Add fs_dax_get() func to prepare dax for fs-dax usage
	* dax: Add dax_set_ops() for setting dax_operations at bind time
	* dax: Add dax_operations for use by fs-dax on fsdev dax
	* dax: Save the kva from memremap
	* dax: add fsdev.c driver for fs-dax on character dax
	* dax: Factor out dax_folio_reset_order() helper
	* dax: move dax_pgoff_to_phys from [drivers/dax/] device.c to bus.c

----------------------------------------------------------------
John Groves (9):
      dax: move dax_pgoff_to_phys from [drivers/dax/] device.c to bus.c
      dax: Factor out dax_folio_reset_order() helper
      dax: add fsdev.c driver for fs-dax on character dax
      dax: Save the kva from memremap
      dax: Add dax_operations for use by fs-dax on fsdev dax
      dax: Add dax_set_ops() for setting dax_operations at bind time
      dax: Add fs_dax_get() func to prepare dax for fs-dax usage
      dax: export dax_dev_get()
      dax/fsdev: fix uninitialized kaddr in fsdev_dax_zero_page_range()

 MAINTAINERS               |   8 ++
 drivers/dax/Kconfig       |   5 +
 drivers/dax/Makefile      |   2 +
 drivers/dax/bus.c         |  22 ++-
 drivers/dax/bus.h         |   3 +
 drivers/dax/dax-private.h |   4 +
 drivers/dax/device.c      |  23 ---
 drivers/dax/fsdev.c       | 349 ++++++++++++++++++++++++++++++++++++++++++++++
 drivers/dax/super.c       | 107 +++++++++++++-
 fs/dax.c                  |  74 +++++++---
 include/linux/dax.h       |  19 ++-
 11 files changed, 566 insertions(+), 50 deletions(-)
 create mode 100644 drivers/dax/fsdev.c

             reply	other threads:[~2026-04-21 19:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 19:35 Ira Weiny [this message]
2026-04-21 21:56 ` [GIT PULL] DAX for 7.1 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=69e7d1949ebcc_7d12a10098@iweiny-mobl.notmuch \
    --to=ira.weiny@intel.com \
    --cc=John@groves.net \
    --cc=alison.schofield@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=djbw@kernel.org \
    --cc=jgroves@micron.com \
    --cc=jic23@kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --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