From: "Cheatham, Benjamin" <benjamin.cheatham@amd.com>
To: Gregory Price <gourry@gourry.net>, <linux-cxl@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <kernel-team@meta.com>,
<dave@stgolabs.net>, <jonathan.cameron@huawei.com>,
<dave.jiang@intel.com>, <alison.schofield@intel.com>,
<vishal.l.verma@intel.com>, <ira.weiny@intel.com>,
<dan.j.williams@intel.com>
Subject: Re: [PATCH] cxl/core: fix test_bit misuse with CXL_DECODER_F_ bitmask flags
Date: Mon, 23 Feb 2026 11:33:13 -0600 [thread overview]
Message-ID: <85d7abf8-3b3c-4199-a680-1453f77b3fd5@amd.com> (raw)
In-Reply-To: <20260221021810.1390342-1-gourry@gourry.net>
On 2/20/2026 8:18 PM, Gregory Price wrote:
> CXL_DECODER_F_LOCK (BIT(4) = 16) and CXL_DECODER_F_NORMALIZED_ADDRESSING
> (BIT(6) = 64) are bit masks, but three call sites pass them to test_bit()
> which expects a bit number.
>
> Replace test_bit() with direct bitmask tests, consistent with every other
> use of these flags.
>
> Fixes: 2230c4bdc412 ("cxl: Add handling of locked CXL decoder")
> Signed-off-by: Gregory Price <gourry@gourry.net>
Alison sent out a patch [1] two weeks ago for this. I suspect you found this bug
independently, so I figured I should point it out. Otherwise, I would add a Reported-by (or some
other tag) with her name.
Thanks,
Ben
[1]: https://lore.kernel.org/linux-cxl/20260206181404.1025991-1-alison.schofield@intel.com/
> ---
> drivers/cxl/core/hdm.c | 2 +-
> drivers/cxl/core/region.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/cxl/core/hdm.c b/drivers/cxl/core/hdm.c
> index b2db5967f5c0..c8fcb9d9aa3d 100644
> --- a/drivers/cxl/core/hdm.c
> +++ b/drivers/cxl/core/hdm.c
> @@ -904,7 +904,7 @@ static void cxl_decoder_reset(struct cxl_decoder *cxld)
> if ((cxld->flags & CXL_DECODER_F_ENABLE) == 0)
> return;
>
> - if (test_bit(CXL_DECODER_F_LOCK, &cxld->flags))
> + if (cxld->flags & CXL_DECODER_F_LOCK)
> return;
>
> if (port->commit_end == id)
> diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
> index bd4c4a4a27da..385be9cb44cd 100644
> --- a/drivers/cxl/core/region.c
> +++ b/drivers/cxl/core/region.c
> @@ -1100,12 +1100,12 @@ static int cxl_rr_assign_decoder(struct cxl_port *port, struct cxl_region *cxlr,
> static void cxl_region_setup_flags(struct cxl_region *cxlr,
> struct cxl_decoder *cxld)
> {
> - if (test_bit(CXL_DECODER_F_LOCK, &cxld->flags)) {
> + if (cxld->flags & CXL_DECODER_F_LOCK) {
> set_bit(CXL_REGION_F_LOCK, &cxlr->flags);
> clear_bit(CXL_REGION_F_NEEDS_RESET, &cxlr->flags);
> }
>
> - if (test_bit(CXL_DECODER_F_NORMALIZED_ADDRESSING, &cxld->flags))
> + if (cxld->flags & CXL_DECODER_F_NORMALIZED_ADDRESSING)
> set_bit(CXL_REGION_F_NORMALIZED_ADDRESSING, &cxlr->flags);
> }
>
next prev parent reply other threads:[~2026-02-23 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 2:18 Gregory Price
2026-02-23 17:33 ` Cheatham, Benjamin [this message]
2026-02-23 17:45 ` Gregory Price
2026-02-23 18:04 ` Dave Jiang
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=85d7abf8-3b3c-4199-a680-1453f77b3fd5@amd.com \
--to=benjamin.cheatham@amd.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=gourry@gourry.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=kernel-team@meta.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®