mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Tomasz Wolski <tomasz.wolski@fujitsu.com>
Cc: <smita.koralahallichannabasappa@amd.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 v3] dax/bus: Upgrade resource conflict message to dev_err() in alloc_dax_region()
Date: Mon, 1 Jun 2026 17:40:35 -0700	[thread overview]
Message-ID: <ah4mgyJZsEcsYiu3@aschofie-mobl2.lan> (raw)
In-Reply-To: <20260528064546.23362-1-tomasz.wolski@fujitsu.com>

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



      parent reply	other threads:[~2026-06-02  0:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28  6:45 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 [this message]

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=ah4mgyJZsEcsYiu3@aschofie-mobl2.lan \
    --to=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®