From: Dave Jiang <dave.jiang@intel.com>
To: Li Ming <ming.li@zohomail.com>,
Alison Schofield <alison.schofield@intel.com>
Cc: linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jic23@kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>, Dan Williams <djbw@kernel.org>
Subject: Re: [PATCH] cxl/region: Fix out of bounds access in cxl_cancel_auto_attach()
Date: Fri, 22 May 2026 08:44:20 -0700 [thread overview]
Message-ID: <e0ad8650-414a-4f9b-a419-60476c44e6a2@intel.com> (raw)
In-Reply-To: <f27fef4c-6b27-4027-88bb-0db57c1b346a@zohomail.com>
On 5/22/26 1:49 AM, Li Ming wrote:
>
> 在 2026/5/21 14:52, Alison Schofield 写道:
>> On Wed, May 20, 2026 at 07:59:21AM -0700, Dave Jiang wrote:
>>>
>>> On 5/20/26 5:30 AM, Li Ming wrote:
>>>> 在 2026/5/20 01:18, Dave Jiang 写道:
>>>>> On 5/19/26 6:23 AM, Li Ming wrote:
>>>>>> In cxl_cancel_auto_attach(), it assumes cxled->pos is a valid index for
>>>>>> accessing p->targets[]. However, cxled->pos can be set to -ENXIO in
>>>>> It can be set to other error codes I think? I would just s/-ENXIO/negative errno/
>>>> Sure, Will do that.
>>>>>> cxl_region_sort_targets() if cxl_calc_interleave_pos() fails. This
>>>>>> causes the driver to use a negative index to access p->targets[],
>>>>>> resulting in out-of-bounds access.
>>>>>>
>>>>>> Fix it by walking p->targets[] instead of using cxled->pos directly.
>>>>> Does the comment in cxl_region_sort_targets() need to be updated with the new changes?
>>>> I'm not sure how to update the comment in cxl_region_sort_targets(). Any suggestion?
>>> idk if we should just drop it entirely since the comment is no longer true. At least that second part. Alison?
>> I'd like to see it replaced w this so we continue to have the
>> debug info, but stop the lie that led to this issue.
>>
>> /*
>> * Record that sorting failed, but still continue to calc
>> * cxled->pos so that cxl_calc_interleave_pos() emits its
>> * dev_dbg() for every member, which is useful for auto
>> * discovery debug.
>> */
>>
>> snip
>>
>>>>>> +static int cxl_region_remove_target(struct device *dev, void *data)
>>>>>> {
>>>>>> - const struct cxl_endpoint_decoder *cxled = data;
>>>>>> + struct cxl_endpoint_decoder *cxled = data;
>>>>>> struct cxl_region_params *p;
>>>>>> struct cxl_region *cxlr;
>>>>>> + int i;
>>>>>> if (!is_cxl_region(dev))
>>>>>> return 0;
>>>>>> cxlr = to_cxl_region(dev);
>>>>>> p = &cxlr->params;
>>>>>> - return p->targets[cxled->pos] == cxled;
>>>>>> + for (i = 0; i < p->nr_targets; i++) {
>>>>>> + if (p->targets[i] == cxled) {
>>>>>> + p->nr_targets--;
>>>>>> + cxled->state = CXL_DECODER_STATE_AUTO;
>>>>>> + cxled->pos = -1;
>>>>>> + p->targets[i] = NULL;
>>>>>> +
>>>>>> + return 1;
>>>>>> + }
>>>>>> + }
>> Sashiko review looks like it is calling out a valid 'hole' issue above.
>> Does the array need to be compacted when we remove an entry that is not
>> the last. That would keep nr_targets same as 'first free slot', so
>> there are no NULL holes. I think that fix goes in a separate patch.
>
> Good catch, how about using p->interleave_ways instead of p->nr_targets as the loop condition? I think it can solve the problem.
>
> BTW, where did you get the Sashiko review? I didn't get any email from it.
You'll have to look, unless you cc Sachiko with your patch submission. I've asked to have linux-cxl added to Sachiko review.
https://sashiko.dev/#/?list=org.kernel.vger.linux-cxl
>
>
> Ming
>
prev parent reply other threads:[~2026-05-22 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 13:23 Li Ming
2026-05-19 17:18 ` Dave Jiang
2026-05-20 12:30 ` Li Ming
2026-05-20 14:59 ` Dave Jiang
2026-05-21 6:52 ` Alison Schofield
2026-05-22 8:49 ` Li Ming
2026-05-22 15:44 ` 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=e0ad8650-414a-4f9b-a419-60476c44e6a2@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=dave@stgolabs.net \
--cc=djbw@kernel.org \
--cc=ira.weiny@intel.com \
--cc=jic23@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.com \
--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®