From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: <alison.schofield@intel.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
Dave Jiang <dave.jiang@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH] cxl/region: Avoid null pointer dereference in region lookup
Date: Tue, 4 Jun 2024 17:37:49 +0100 [thread overview]
Message-ID: <20240604173749.00002451@Huawei.com> (raw)
In-Reply-To: <20240604003609.202682-1-alison.schofield@intel.com>
On Mon, 3 Jun 2024 17:36:09 -0700
alison.schofield@intel.com wrote:
> From: Alison Schofield <alison.schofield@intel.com>
>
> cxl_dpa_to_region() looks up a region based on a memdev and DPA.
> It wrongly assumes an endpoint found mapping the DPA is also of
> a fully assembled region. When not true it leads to a null pointer
> dereference looking up the region name.
>
> This appears during testing of region lookup after a failure to
> assemble a BIOS defined region or if the lookup raced with the
> assembly of the BIOS defined region.
>
> Failure to clean up BIOS defined regions that fail assembly is an
> issue in itself and a fix to that problem will alleviate some of
> the impact. It will not alleviate the race condition so let's harden
> this path.
>
> The behavior change is that the kernel oops due to a null pointer
> dereference is replaced with a dev_dbg() message noting that an
> endpoint was mapped.
>
> Additional comments are added so that future users of this function
> can more clearly understand what it provides.
>
> Fixes: 0a105ab28a4d ("cxl/memdev: Warn of poison inject or clear to a mapped region")
> Signed-off-by: Alison Schofield <alison.schofield@intel.com>
Nasty corner case. Fix looks correct to me.
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
> drivers/cxl/core/region.c | 19 +++++++++++++++----
> 1 file changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
> index 3c2b6144be23..88051bb673bf 100644
> --- a/drivers/cxl/core/region.c
> +++ b/drivers/cxl/core/region.c
> @@ -2688,22 +2688,33 @@ static int __cxl_dpa_to_region(struct device *dev, void *arg)
> {
> struct cxl_dpa_to_region_context *ctx = arg;
> struct cxl_endpoint_decoder *cxled;
> + struct cxl_region *cxlr;
> u64 dpa = ctx->dpa;
>
> if (!is_endpoint_decoder(dev))
> return 0;
>
> cxled = to_cxl_endpoint_decoder(dev);
> - if (!cxled->dpa_res || !resource_size(cxled->dpa_res))
> + if (!cxled || !cxled->dpa_res || !resource_size(cxled->dpa_res))
> return 0;
>
> if (dpa > cxled->dpa_res->end || dpa < cxled->dpa_res->start)
> return 0;
>
> - dev_dbg(dev, "dpa:0x%llx mapped in region:%s\n", dpa,
> - dev_name(&cxled->cxld.region->dev));
> + /*
> + * Stop the region search (return 1) when an endpoint mapping is
> + * found. The region may not be fully constructed so offering
> + * the cxlr in the context structure is not guaranteed.
> + */
> + cxlr = cxled->cxld.region;
> + if (cxlr)
> + dev_dbg(dev, "dpa:0x%llx mapped in region:%s\n", dpa,
> + dev_name(&cxlr->dev));
> + else
> + dev_dbg(dev, "dpa:0x%llx mapped in endpoint:%s\n", dpa,
> + dev_name(dev));
>
> - ctx->cxlr = cxled->cxld.region;
> + ctx->cxlr = cxlr;
>
> return 1;
> }
>
> base-commit: 49ba7b515c4c0719b866d16f068e62d16a8a3dd1
next prev parent reply other threads:[~2024-06-04 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 0:36 [PATCH] cxl/region: Avoid null pointer dereference in region lookup alison.schofield
2024-06-04 16:37 ` Jonathan Cameron [this message]
2024-06-04 17:47 ` Dan Williams
2024-06-05 0:43 ` Alison Schofield
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=20240604173749.00002451@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@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