From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,vishal.l.verma@intel.com,stable@vger.kernel.org,joao.m.martins@oracle.com,dave.jiang@intel.com,alison.schofield@intel.com,yaojiale02@163.com,akpm@linux-foundation.org
Subject: + dax-device-defer-publishing-the-dynamic-pgmap.patch added to mm-new branch
Date: Sun, 27 Sep 2026 13:27:52 -0700 [thread overview]
Message-ID: <20260927202753.4A34B1F000FF@smtp.kernel.org> (raw)
The patch titled
Subject: dax/device: defer publishing the dynamic pgmap
has been added to the -mm mm-new branch. Its filename is
dax-device-defer-publishing-the-dynamic-pgmap.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/dax-device-defer-publishing-the-dynamic-pgmap.patch
This patch will later appear in the mm-new branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Note, mm-new is a provisional staging ground for work-in-progress
patches, and acceptance into mm-new is a notification for others take
notice and to finish up reviews. Please do not hesitate to respond to
review feedback and post updated versions to replace or incrementally
fixup patches in mm-new.
The mm-new branch of mm.git is not included in linux-next
If a few days of testing in mm-new is successful, the patch will me moved
into mm.git's mm-unstable branch, which is included in linux-next
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via various
branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there most days
------------------------------------------------------
From: Jiale Yao <yaojiale02@163.com>
Subject: dax/device: defer publishing the dynamic pgmap
Date: Sun, 27 Sep 2026 19:47:36 +0800
The dynamic device-dax probe path publishes its devm-allocated pgmap
before several operations that can still fail. If one of them fails,
devres frees the pgmap while dev_dax->pgmap remains non-NULL. A later
bind then fails the dynamic-dax invariant check and leaves the device
unusable until its region is recreated.
Defer assigning dev_dax->pgmap until the final devm action has been
installed and probe can no longer fail. A failed probe then never
publishes the temporary pgmap.
Link: https://lore.kernel.org/20260927114736.1113965-1-yaojiale02@163.com
Fixes: fc65c4eb0b2a ("device-dax: ensure dev_dax->pgmap is valid for dynamic devices")
Signed-off-by: Jiale Yao <yaojiale02@163.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Vishal Verma <vishal.l.verma@intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>
Cc: Alison Schofield <alison.schofield@intel.com>
Cc: Joao Martins <joao.m.martins@oracle.com>
Cc: <stable@vger.kernel.org>
---
drivers/dax/device.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
--- a/drivers/dax/device.c~dax-device-defer-publishing-the-dynamic-pgmap
+++ a/drivers/dax/device.c
@@ -409,7 +409,6 @@ static int dev_dax_probe(struct dev_dax
return -ENOMEM;
pgmap->nr_range = dev_dax->nr_range;
- dev_dax->pgmap = pgmap;
for (i = 0; i < dev_dax->nr_range; i++) {
struct range *range = &dev_dax->ranges[i].range;
@@ -450,7 +449,13 @@ static int dev_dax_probe(struct dev_dax
return rc;
run_dax(dax_dev);
- return devm_add_action_or_reset(dev, dev_dax_kill, dev_dax);
+ rc = devm_add_action_or_reset(dev, dev_dax_kill, dev_dax);
+ if (rc)
+ return rc;
+
+ /* Probe can no longer fail; expose the pgmap via dev_dax. */
+ dev_dax->pgmap = pgmap;
+ return 0;
}
static struct dax_device_driver device_dax_driver = {
_
Patches currently in -mm which might be from yaojiale02@163.com are
dax-device-defer-publishing-the-dynamic-pgmap.patch
reply other threads:[~2026-09-27 20:27 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=20260927202753.4A34B1F000FF@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=joao.m.martins@oracle.com \
--cc=mm-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=yaojiale02@163.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.