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 <[email protected]>
> Link:
> https://lore.kernel.org/linux-cxl/[email protected]/
> Signed-off-by: Tomasz Wolski <[email protected]>
Reviewed-by: Dave Jiang <[email protected]>
> ---
> 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;
> }
