mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Muchun Song <muchun.song@linux.dev>
To: Alison Schofield <alison.schofield@intel.com>
Cc: Muchun Song <songmuchun@bytedance.com>,
	Dan Williams <djbw@kernel.org>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Dave Jiang <dave.jiang@intel.com>,
	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
Subject: Re: [PATCH v3 1/2] dax/bus: fix mapping attribute error reporting
Date: Tue, 13 Oct 2026 14:27:15 +0800	[thread overview]
Message-ID: <AAB2A53F-1D2B-44FA-9D36-C393444C6DAA@linux.dev> (raw)
In-Reply-To: <as13np-95gSaBbQm@aschofie-mobl2.lan>



> On Oct 13, 2026, at 08:13, Alison Schofield <alison.schofield@intel.com> wrote:
> 
> On Thu, Sep 24, 2026 at 10:50:34AM +0800, 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.
> 
> Reviewed-by: Alison Schofield <alison.schofield@intel.com>

Thanks.

> 
> Will modify subject line upon applying like so:
> dax/bus: Return errors for invalid mapping requests

No problem.

Thanks,
Muchun

  reply	other threads:[~2026-10-13  6:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24  2:50 [PATCH v3 0/2] dax: Fix Device DAX range allocation validation Muchun Song
2026-09-24  2:50 ` [PATCH v3 1/2] dax/bus: fix mapping attribute error reporting Muchun Song
2026-10-13  0:13   ` Alison Schofield
2026-10-13  6:27     ` Muchun Song [this message]
2026-10-13  2:31   ` jianyungao89
2026-09-24  2:50 ` [PATCH v3 2/2] dax/bus: fix Device DAX range alignment validation Muchun Song
2026-10-13  0:20   ` Alison Schofield
2026-10-13  8:45     ` 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=AAB2A53F-1D2B-44FA-9D36-C393444C6DAA@linux.dev \
    --to=muchun.song@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=alison.schofield@intel.com \
    --cc=dave.jiang@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=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
all inboxes | Powered by JetHome®