Linux CXL
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Purva Yeshi <purvayeshi550@gmail.com>, <dave@stgolabs.net>,
	<jonathan.cameron@huawei.com>, <dave.jiang@intel.com>,
	<vishal.l.verma@intel.com>, <ira.weiny@intel.com>,
	<ming.li@zohomail.com>, <huang.ying.caritas@gmail.com>,
	<linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cxl: core: Initialize eiw and eig to fix potential uninitialized use
Date: Tue, 13 May 2025 11:52:25 -0700	[thread overview]
Message-ID: <aCOU6V2mece-gjWz@aschofie-mobl2.lan> (raw)
In-Reply-To: <680682dabbd09_71fe29462@dwillia2-xfh.jf.intel.com.notmuch>

On Mon, Apr 21, 2025 at 10:39:38AM -0700, Dan Williams wrote:
> Purva Yeshi wrote:
> > Fix Smatch-detected issue:
> > 
> > drivers/cxl/core/region.c:1292 check_interleave_cap()
> > error: uninitialized symbol 'eiw'.
> > drivers/cxl/core/region.c:1297 check_interleave_cap()
> > error: uninitialized symbol 'eig'.
> > drivers/cxl/core/region.c:1299 check_interleave_cap()
> > error: uninitialized symbol 'eig'.
> > 
> > Smatch reports possible uninitialized usage of these variables if
> > the helper functions ways_to_eiw() or granularity_to_eig() fail to
> > assign values under certain conditions.
> > 
> > Initialize the eiw and eig variables to zero when they are declared
> > in check_interleave_cap() to prevent potential use of uninitialized
> > values.
> > 

Hi Purva,

We'd like to see this patch revised and resubmitted. It is a
good cleanup!

Go ahead and send a v2 with Dan's suggestion as the solution.
There's a couple of options for the tags. Here I think it is
good to add this tag: 

Suggested-by: Dan Williams <dan.j.williams@intel.com>

followed by your Signed-off-by tag.


> > Signed-off-by: Purva Yeshi <purvayeshi550@gmail.com>
> > ---
You'll add a changelog in v2 here, below the ---,  something like:
Changes in v2:
- init eiw and eig in their helper functions (Dan)


Thanks,
Alison

> >  drivers/cxl/core/region.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
> > index c3f4dc244df7..edf8636f190a 100644
> > --- a/drivers/cxl/core/region.c
> > +++ b/drivers/cxl/core/region.c
> > @@ -1266,8 +1266,8 @@ static int check_interleave_cap(struct cxl_decoder *cxld, int iw, int ig)
> >  	struct cxl_port *port = to_cxl_port(cxld->dev.parent);
> >  	struct cxl_hdm *cxlhdm = dev_get_drvdata(&port->dev);
> >  	unsigned int interleave_mask;
> > -	u8 eiw;
> > -	u16 eig;
> > +	u8 eiw = 0;
> > +	u16 eig = 0;
> 
> I appreciate that this quiets the warning, but it is leaving a trip
> hazard for future code refactoring. I would prefer to make this scenario
> harder to repeat in the future with something like:
> 
> diff --git a/drivers/cxl/cxl.h b/drivers/cxl/cxl.h
> index be8a7dc77719..5f20919207ae 100644
> --- a/drivers/cxl/cxl.h
> +++ b/drivers/cxl/cxl.h
> @@ -107,6 +107,7 @@ static inline int eiw_to_ways(u8 eiw, unsigned int *ways)
>  
>  static inline int granularity_to_eig(int granularity, u16 *eig)
>  {
> +	*eig = 0;
>  	if (granularity > SZ_16K || granularity < CXL_DECODER_MIN_GRANULARITY ||
>  	    !is_power_of_2(granularity))
>  		return -EINVAL;
> @@ -116,6 +117,7 @@ static inline int granularity_to_eig(int granularity, u16 *eig)
>  
>  static inline int ways_to_eiw(unsigned int ways, u8 *eiw)
>  {
> +	*eiw = 0;
>  	if (ways > 16)
>  		return -EINVAL;
>  	if (is_power_of_2(ways)) {

      reply	other threads:[~2025-05-13 18:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-19 20:35 [PATCH] cxl: core: Initialize eiw and eig to fix potential uninitialized use Purva Yeshi
2025-04-20 10:43 ` Li Ming
2025-04-21 15:40   ` Gregory Price
2025-04-21 15:41 ` Gregory Price
2025-04-21 17:39 ` Dan Williams
2025-05-13 18:52   ` Alison Schofield [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=aCOU6V2mece-gjWz@aschofie-mobl2.lan \
    --to=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=huang.ying.caritas@gmail.com \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.li@zohomail.com \
    --cc=purvayeshi550@gmail.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