* Re: [PATCH v3] dax/bus: Upgrade resource conflict message to dev_err() in alloc_dax_region()
2026-05-28 6:45 [PATCH v3] dax/bus: Upgrade resource conflict message to dev_err() in alloc_dax_region() Tomasz Wolski
@ 2026-05-28 8:33 ` Richard Cheng
2026-05-28 15:37 ` Dave Jiang
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Richard Cheng @ 2026-05-28 8:33 UTC (permalink / raw)
To: Tomasz Wolski
Cc: smita.koralahallichannabasappa, alison.schofield, dan.j.williams,
linux-cxl, linux-fsdevel, linux-kernel, linux-pm, nvdimm, ardb,
benjamin.cheatham, dave.jiang, jonathan.cameron
On Thu, May 28, 2026 at 08:45:46AM +0800, Tomasz Wolski 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.
>
> Promote the log level from dev_dbg() to dev_err() so that the conflict
> is visible by default without requiring dynamic debug to be enabled.
>
> 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>
> ---
> drivers/dax/bus.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dax/bus.c b/drivers/dax/bus.c
> index 68437c05e21d..cd963eeeef7b 100644
> --- a/drivers/dax/bus.c
> +++ b/drivers/dax/bus.c
> @@ -672,7 +672,7 @@ struct dax_region *alloc_dax_region(struct device *parent, int region_id,
>
> rc = request_resource(&dax_regions, &dax_region->res);
> if (rc) {
> - dev_dbg(parent, "dax_region resource conflict for %pR\n",
> + dev_err(parent, "dax_region resource conflict for %pR\n",
> &dax_region->res);
> goto err_res;
> }
> --
> 2.47.3
>
Reviewed-by: Richard Cheng <icheng@nvidia.com>
Best regards,
Richard Cheng.
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH v3] dax/bus: Upgrade resource conflict message to dev_err() in alloc_dax_region()
2026-05-28 6:45 [PATCH v3] dax/bus: Upgrade resource conflict message to dev_err() in alloc_dax_region() Tomasz Wolski
2026-05-28 8:33 ` Richard Cheng
@ 2026-05-28 15:37 ` Dave Jiang
2026-05-28 15:59 ` Alison Schofield
2026-06-02 0:40 ` Alison Schofield
3 siblings, 0 replies; 5+ messages in thread
From: Dave Jiang @ 2026-05-28 15:37 UTC (permalink / raw)
To: Tomasz Wolski, smita.koralahallichannabasappa, alison.schofield,
dan.j.williams
Cc: icheng, linux-cxl, linux-fsdevel, linux-kernel, linux-pm, nvdimm,
ardb, benjamin.cheatham, jonathan.cameron
On 5/27/26 11:45 PM, Tomasz Wolski 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.
>
> Promote the log level from dev_dbg() to dev_err() so that the conflict
> is visible by default without requiring dynamic debug to be enabled.
>
> 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>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/dax/bus.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dax/bus.c b/drivers/dax/bus.c
> index 68437c05e21d..cd963eeeef7b 100644
> --- a/drivers/dax/bus.c
> +++ b/drivers/dax/bus.c
> @@ -672,7 +672,7 @@ struct dax_region *alloc_dax_region(struct device *parent, int region_id,
>
> rc = request_resource(&dax_regions, &dax_region->res);
> if (rc) {
> - dev_dbg(parent, "dax_region resource conflict for %pR\n",
> + dev_err(parent, "dax_region resource conflict for %pR\n",
> &dax_region->res);
> goto err_res;
> }
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH v3] dax/bus: Upgrade resource conflict message to dev_err() in alloc_dax_region()
2026-05-28 6:45 [PATCH v3] dax/bus: Upgrade resource conflict message to dev_err() in alloc_dax_region() Tomasz Wolski
2026-05-28 8:33 ` Richard Cheng
2026-05-28 15:37 ` Dave Jiang
@ 2026-05-28 15:59 ` Alison Schofield
2026-06-02 0:40 ` Alison Schofield
3 siblings, 0 replies; 5+ messages in thread
From: Alison Schofield @ 2026-05-28 15:59 UTC (permalink / raw)
To: Tomasz Wolski
Cc: smita.koralahallichannabasappa, dan.j.williams, icheng,
linux-cxl, linux-fsdevel, linux-kernel, linux-pm, nvdimm, ardb,
benjamin.cheatham, dave.jiang, jonathan.cameron
On Thu, May 28, 2026 at 08:45:46AM +0200, Tomasz Wolski 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.
>
> Promote the log level from dev_dbg() to dev_err() so that the conflict
> is visible by default without requiring dynamic debug to be enabled.
Reviewed-by: Alison Schofield <alison.schofield@intel.com>
>
> 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>
> ---
> drivers/dax/bus.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dax/bus.c b/drivers/dax/bus.c
> index 68437c05e21d..cd963eeeef7b 100644
> --- a/drivers/dax/bus.c
> +++ b/drivers/dax/bus.c
> @@ -672,7 +672,7 @@ struct dax_region *alloc_dax_region(struct device *parent, int region_id,
>
> rc = request_resource(&dax_regions, &dax_region->res);
> if (rc) {
> - dev_dbg(parent, "dax_region resource conflict for %pR\n",
> + dev_err(parent, "dax_region resource conflict for %pR\n",
> &dax_region->res);
> goto err_res;
> }
> --
> 2.47.3
>
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH v3] dax/bus: Upgrade resource conflict message to dev_err() in alloc_dax_region()
2026-05-28 6:45 [PATCH v3] dax/bus: Upgrade resource conflict message to dev_err() in alloc_dax_region() Tomasz Wolski
` (2 preceding siblings ...)
2026-05-28 15:59 ` Alison Schofield
@ 2026-06-02 0:40 ` Alison Schofield
3 siblings, 0 replies; 5+ messages in thread
From: Alison Schofield @ 2026-06-02 0:40 UTC (permalink / raw)
To: Tomasz Wolski
Cc: smita.koralahallichannabasappa, dan.j.williams, icheng,
linux-cxl, linux-fsdevel, linux-kernel, linux-pm, nvdimm, ardb,
benjamin.cheatham, dave.jiang, jonathan.cameron
On Thu, May 28, 2026 at 08:45:46AM +0200, Tomasz Wolski 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.
>
> Promote the log level from dev_dbg() to dev_err() so that the conflict
> is visible by default without requiring dynamic debug to be enabled.
>
> 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>
> ---
Applied to nvdimm/nvdimm.git (libnvdimm-for-next)
https://git.kernel.org/nvdimm/nvdimm/c/cd1a8d788763
^ permalink raw reply [flat|nested] 5+ messages in thread