From: Alison Schofield <alison.schofield@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <dave.jiang@intel.com>, <linux-kernel@vger.kernel.org>,
<nvdimm@lists.linux.dev>, <vishal.l.verma@intel.com>
Subject: [GIT PULL] NVDIMM and DAX for 7.4
Date: Sun, 25 Oct 2026 20:42:01 -0700 [thread overview]
Message-ID: <at7MCT6uhsn0B4ER@aschofie-mobl2.lan> (raw)
Hi Linus,
Please pull to receive NVDIMM and DAX changes for 7.4:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git tags/libnvdimm-for-7.4
This is a small set of fixes: error handling corrections in the DAX
core and bus code, a fix to the DAX file range comparison helpers, and
two libnvdimm/pmem fixes for error and probe failure paths.
These have all appeared in -next for at least 6 days.
Thank-you,
Alison
---
The following changes since commit 72d3fcf802c45d00b300f25b848a93c3a2bd7c7e:
Linux 7.3-rc5 (2026-09-27 13:55:01 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git tags/libnvdimm-for-7.4
for you to fetch changes up to 9b036546a02c6c9a5133f9c1e93503896595c6ba:
dax: fix wrong error code returned from dax_dedupe_file_range_compare() (2026-10-19 09:43:01 -0700)
----------------------------------------------------------------
NVDIMM and DAX for v7.4
DAX fixes:
dax: fix wrong error code returned from dax_dedupe_file_range_compare()
dax: fix dax_range_compare_iter() to use correct size and address offset
dax: Return errors from dax_core_init()
dax/bus: Return errors for invalid mapping targets
NVDIMM fixes:
libnvdimm: Handle negative return from nvdimm_clear_poison() in nsio_rw_bytes()
nvdimm/pmem: Release gendisk on probe failure
----------------------------------------------------------------
Hemanth Selam (1):
nvdimm/pmem: Release gendisk on probe failure
Jianyun Gao (3):
dax: Return errors from dax_core_init()
dax: fix dax_range_compare_iter() to use correct size and address offset
dax: fix wrong error code returned from dax_dedupe_file_range_compare()
Muchun Song (1):
dax/bus: Return errors for invalid mapping targets
Serhat Kumral (1):
libnvdimm: Handle negative return from nvdimm_clear_poison() in nsio_rw_bytes()
drivers/dax/bus.c | 8 ++++++--
drivers/dax/super.c | 2 +-
drivers/nvdimm/claim.c | 2 +-
drivers/nvdimm/pmem.c | 6 ++++--
fs/dax.c | 14 ++++++++------
5 files changed, 20 insertions(+), 12 deletions(-)
reply other threads:[~2026-10-26 3:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=at7MCT6uhsn0B4ER@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=vishal.l.verma@intel.com \
/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
all inboxes | Powered by JetHome®