From: Dan Carpenter <dan.carpenter@linaro.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [bug report] EDAC/{skx_common,i10nm}: Refactor show_retry_rd_err_log()
Date: Wed, 23 Apr 2025 19:49:45 +0300 [thread overview]
Message-ID: <a9ab50ec-56e3-47dd-9ecd-333fbb1d964b@stanley.mountain> (raw)
In-Reply-To: <DS7PR11MB6077471F9B1B3221DA9FDEE5FCBA2@DS7PR11MB6077.namprd11.prod.outlook.com>
On Wed, Apr 23, 2025 at 04:26:21PM +0000, Luck, Tony wrote:
> > > 362 /* Clear RRL status if RRL in Linux control mode. */
> > > 363 if (retry_rd_err_log == 2 && !j && (log & status_mask))
> > > --> 364 write_imc_reg(imc, ch, offset, width, log &
> > > ~status_mask);
> > >
> > > This will clear the high 32 bits of log.
> >
> > It's OK to clear the high 32 bits of 'log', as we only write the low 32 bits of 'log' to
> > the 1st RRL register, which is a u32 type.
> >
> > To improve code sanity, it might be worthwhile to create a patch that changes
> > 'status_mask' to a u64 type. @Luck, Tony, should I create a fix patch on top of the
> > current patch series to fix this warning?
>
> Qiuxu,
>
> Yes. Write a patch for this and give a Reported-by: credit to Dan.
>
Thanks. But mention what you said that it's a false positive.
It's hard to silence a warning like this in Smatch because you'd need to
read into the write_imc_reg() to see that only 4 byte widths are
supported.
regards,
dan carpenter
prev parent reply other threads:[~2025-04-23 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 8:16 [bug report] EDAC/{skx_common,i10nm}: Refactor show_retry_rd_err_log() Dan Carpenter
2025-04-23 15:38 ` Zhuo, Qiuxu
2025-04-23 16:26 ` Luck, Tony
2025-04-23 16:49 ` Dan Carpenter [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=a9ab50ec-56e3-47dd-9ecd-333fbb1d964b@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=linux-edac@vger.kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=tony.luck@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.