From: Jonathan Cameron <jic23@kernel.org>
To: Tomasz Wolski <tomasz.wolski@fujitsu.com>
Cc: smita.koralahallichannabasappa@amd.com,
alison.schofield@intel.com, dan.j.williams@intel.com,
icheng@nvidia.com, linux-cxl@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, nvdimm@lists.linux.dev,
ardb@kernel.org, benjamin.cheatham@amd.com, dave.jiang@intel.com,
jonathan.cameron@huawei.com
Subject: Re: [PATCH v2] dax/bus: Upgrade resource conflict message to dev_err() in alloc_dax_region()
Date: Tue, 19 May 2026 12:31:12 +0100 [thread overview]
Message-ID: <20260519123112.5b5d34cd@jic23-huawei> (raw)
In-Reply-To: <20260519101832.31988-1-tomasz.wolski@fujitsu.com>
On Tue, 19 May 2026 12:18:32 +0200
Tomasz Wolski <tomasz.wolski@fujitsu.com> wrote:
> The dax_region resource conflict in alloc_dax_region() indicates a
> serious configuration problem — two subsystems (e.g. dax_hmem and
> dax_cxl) are attempting to register overlapping address ranges. This is
> not a transient or debug-level condition; it represents a genuine
> resource conflict that an administrator needs to be aware of.
>
> Switch from request_resource() + dev_dbg() to
> request_resource_conflict() + dev_err() so that the conflict is visible
> by default and the colliding resource is identified in the message.
>
> Suggested-by: Dan Williams <dan.j.williams@intel.com>
> Link: https://lore.kernel.org/linux-cxl/69c1a8d1c0fa9_7ee3100a1@dwillia2-mobl4.notmuch/
> Signed-off-by: Tomasz Wolski <tomasz.wolski@fujitsu.com>
Seems reasonable to me
Reviewed-by: Jonathan Cameron <jic23@kernel.org>
> ---
> drivers/dax/bus.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/dax/bus.c b/drivers/dax/bus.c
> index 68437c05e21d..66413c6c2ba0 100644
> --- a/drivers/dax/bus.c
> +++ b/drivers/dax/bus.c
> @@ -637,7 +637,7 @@ struct dax_region *alloc_dax_region(struct device *parent, int region_id,
> unsigned long flags)
> {
> struct dax_region *dax_region;
> - int rc;
> + struct resource *conflict;
>
> /*
> * The DAX core assumes that it can store its private data in
> @@ -670,10 +670,11 @@ struct dax_region *alloc_dax_region(struct device *parent, int region_id,
> .flags = IORESOURCE_MEM | flags,
> };
>
> - rc = request_resource(&dax_regions, &dax_region->res);
> - if (rc) {
> - dev_dbg(parent, "dax_region resource conflict for %pR\n",
> - &dax_region->res);
> + conflict = request_resource_conflict(&dax_regions, &dax_region->res);
> + if (conflict) {
> + dev_err(parent,
> + "dax_region: can't claim %pR: address conflict with %s %pR\n",
> + &dax_region->res, conflict->name, conflict);
> goto err_res;
> }
>
next prev parent reply other threads:[~2026-05-19 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 10:18 Tomasz Wolski
2026-05-19 11:31 ` Jonathan Cameron [this message]
2026-05-19 23:27 ` Richard Cheng
2026-05-20 0:14 ` kernel test robot
2026-05-20 2:48 ` Alison Schofield
2026-05-20 3:56 ` Dan Williams
2026-05-27 8:03 ` Tomasz Wolski
2026-05-27 18:44 ` Alison Schofield
2026-05-28 6:40 ` Tomasz Wolski
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=20260519123112.5b5d34cd@jic23-huawei \
--to=jic23@kernel.org \
--cc=alison.schofield@intel.com \
--cc=ardb@kernel.org \
--cc=benjamin.cheatham@amd.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=icheng@nvidia.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=smita.koralahallichannabasappa@amd.com \
--cc=tomasz.wolski@fujitsu.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®