Linux CXL
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Vishal Verma <vishal.l.verma@intel.com>
Cc: linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev,
	Dan Williams <dan.j.williams@intel.com>,
	Steven Garcia <steven.garcia@intel.com>
Subject: Re: [ndctl PATCH] libcxl: fix a segfault when memdev->pmem is absent
Date: Wed, 15 Jun 2022 14:46:02 -0700	[thread overview]
Message-ID: <20220615214602.GA1525164@alison-desk> (raw)
In-Reply-To: <20220602154427.462852-1-vishal.l.verma@intel.com>

On Thu, Jun 02, 2022 at 09:44:27AM -0600, Vishal Verma wrote:
> A CXL memdev may not have any persistent capacity, and in this case it
> is possible that a 'pmem' object never gets instantiated. Such a
> scenario would cause free_pmem () to dereference a NULL pointer and
> segfault.
> 
> Fix this by only proceeding in free_pmem() if 'pmem' was valid.
> 
> Fixes: cd1aed6cefe8 ("libcxl: add representation for an nvdimm bridge object")
> Reported-by: Steven Garcia <steven.garcia@intel.com>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
> ---

Reviewed-by: Alison Schofield <alison.schofield@intel.com>

>  cxl/lib/libcxl.c | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/cxl/lib/libcxl.c b/cxl/lib/libcxl.c
> index 1ad4a0b..2578a43 100644
> --- a/cxl/lib/libcxl.c
> +++ b/cxl/lib/libcxl.c
> @@ -50,9 +50,11 @@ struct cxl_ctx {
>  
>  static void free_pmem(struct cxl_pmem *pmem)
>  {
> -	free(pmem->dev_buf);
> -	free(pmem->dev_path);
> -	free(pmem);
> +	if (pmem) {
> +		free(pmem->dev_buf);
> +		free(pmem->dev_path);
> +		free(pmem);
> +	}
>  }
>  
>  static void free_memdev(struct cxl_memdev *memdev, struct list_head *head)
> 
> base-commit: 4229f2694e8887a47c636a54130cff0d65f2e995
> -- 
> 2.36.1
> 
> 

  reply	other threads:[~2022-06-15 21:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 15:44 [ndctl PATCH] libcxl: fix a segfault when memdev->pmem is absent Vishal Verma
2022-06-15 21:46 ` Alison Schofield [this message]
2022-06-16 17:19 ` [PATCH] " Davidlohr Bueso

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=20220615214602.GA1525164@alison-desk \
    --to=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=steven.garcia@intel.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