From: Dave Jiang <dave.jiang@intel.com>
To: Gregory Price <gourry@gourry.net>,
"Cheatham, Benjamin" <benjamin.cheatham@amd.com>
Cc: linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, dave@stgolabs.net,
jonathan.cameron@huawei.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:04:32 -0700 [thread overview]
Message-ID: <8e3f7f91-99f3-4439-b08c-6bd04c6bf688@intel.com> (raw)
In-Reply-To: <aZySU-tcjVvYcb23@gourry-fedora-PF4VCD3F>
On 2/23/26 10:45 AM, Gregory Price wrote:
> On Mon, Feb 23, 2026 at 11:33:13AM -0600, Cheatham, Benjamin wrote:
>> 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/
>
> Ah, yeah, missed this, and did find independently when testing unbinds.
>
> Wasn't on cxl/next so I thought it hadn't been found yet.
Yeah waiting on 7.0-rc1 for cxl/fixes. I also asked her to split the patches into 2 fixes. But if you don't mind go add your review tag that'd be great! :)
>
> Cool, thanks!
> ~Gregory
prev parent reply other threads:[~2026-02-23 18:04 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
2026-02-23 17:45 ` Gregory Price
2026-02-23 18:04 ` Dave Jiang [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=8e3f7f91-99f3-4439-b08c-6bd04c6bf688@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=benjamin.cheatham@amd.com \
--cc=dan.j.williams@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®