From: Dave Jiang <dave.jiang@intel.com>
To: Muchun Song <songmuchun@bytedance.com>,
Dan Williams <djbw@kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Alison Schofield <alison.schofield@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Joao Martins <joao.m.martins@oracle.com>,
nvdimm@lists.linux.dev, linux-cxl@vger.kernel.org,
linux-kernel@vger.kernel.org, muchun.song@linux.dev
Subject: Re: [PATCH v2 1/2] dax/bus: fix mapping attribute error reporting
Date: Tue, 22 Sep 2026 10:28:33 -0700 [thread overview]
Message-ID: <af3edb82-5247-461e-a5c4-e63476e69e25@intel.com> (raw)
In-Reply-To: <20260922082551.874901-2-songmuchun@bytedance.com>
On 9/22/26 1:25 AM, Muchun Song wrote:
> After the DAX configuration locking was converted to rwsems, successful
> lock acquisition leaves rc set to zero in mapping_store(). Two error
> paths can return this stale value: an unbound region driver and a
> misaligned range size. The sysfs write therefore reports success without
> allocating the requested range.
>
> Return -ENXIO when the region driver is not bound and -EINVAL when the
> range size is misaligned.
>
> Fixes: c05ae9d85b47 ("dax/bus.c: replace driver-core lock usage by a local rwsem")
> Assisted-by: LLM
> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> v2:
> - Return explicit errors before Device DAX range allocation
> (suggested by Dave Jiang)
> - Move the patch before range alignment validation for independent
> backports (suggested by Dave Jiang)
> ---
> drivers/dax/bus.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/dax/bus.c b/drivers/dax/bus.c
> index b809e1a264af..e40c25401cf0 100644
> --- a/drivers/dax/bus.c
> +++ b/drivers/dax/bus.c
> @@ -1192,7 +1192,7 @@ static ssize_t mapping_store(struct device *dev, struct device_attribute *attr,
> return rc;
> if (!dax_region->dev->driver) {
> up_write(&dax_region_rwsem);
> - return rc;
> + return -ENXIO;
> }
> rc = down_write_killable(&dax_dev_rwsem);
> if (rc) {
> @@ -1201,8 +1201,12 @@ static ssize_t mapping_store(struct device *dev, struct device_attribute *attr,
> }
>
> to_alloc = range_len(&r);
> - if (alloc_is_aligned(dev_dax, to_alloc))
> + if (!alloc_is_aligned(dev_dax, to_alloc)) {
> + dev_dbg(dev, "%s: size: %zu misaligned\n", __func__, to_alloc);
> + rc = -EINVAL;
> + } else {
> rc = alloc_dev_dax_range(dev_dax, r.start, to_alloc);
> + }
> up_write(&dax_dev_rwsem);
> up_write(&dax_region_rwsem);
>
next prev parent reply other threads:[~2026-09-22 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 8:25 [PATCH v2 0/2] dax: Fix Device DAX range allocation validation Muchun Song
2026-09-22 8:25 ` [PATCH v2 1/2] dax/bus: fix mapping attribute error reporting Muchun Song
2026-09-22 17:28 ` Dave Jiang [this message]
2026-09-22 8:25 ` [PATCH v2 2/2] dax/bus: fix Device DAX range alignment validation Muchun Song
2026-09-22 8:37 ` sashiko-bot
2026-09-23 6:00 ` Muchun Song
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=af3edb82-5247-461e-a5c4-e63476e69e25@intel.com \
--to=dave.jiang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=djbw@kernel.org \
--cc=joao.m.martins@oracle.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muchun.song@linux.dev \
--cc=nvdimm@lists.linux.dev \
--cc=songmuchun@bytedance.com \
--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