From: Joe Perches <joe@perches.com>
To: Xiongfeng Wang <wangxiongfeng2@huawei.com>,
Borislav Petkov <bp@alien8.de>
Cc: mchehab@kernel.org, tony.luck@intel.com,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] EDAC/mc_sysfs: Add missing newlines when printing {max,dimm}_location
Date: Thu, 17 Sep 2020 08:28:12 -0700 [thread overview]
Message-ID: <707865b7ccc9168177940cd4f63cf7cb9ead2d63.camel@perches.com> (raw)
In-Reply-To: <591e613e-0b53-028f-08fd-3d62a35b8c4f@huawei.com>
On Thu, 2020-09-17 at 19:38 +0800, Xiongfeng Wang wrote:
> On 2020/9/17 1:00, Borislav Petkov wrote:
> > On Mon, Sep 14, 2020 at 10:48:54AM +0800, Xiongfeng Wang wrote:
> > > @@ -813,15 +817,21 @@ static ssize_t mci_max_location_show(struct device *dev,
> > > char *data)
> > > {
> > > struct mem_ctl_info *mci = to_mci(dev);
> > > - int i;
> > > + int i, n;
> > > char *p = data;
> > > + unsigned int len = PAGE_SIZE;
> > >
> > > for (i = 0; i < mci->n_layers; i++) {
> > > - p += sprintf(p, "%s %d ",
> > > + n = snprintf(p, len, "%s %d ",
> > > edac_layer_name[mci->layers[i].type],
> > > mci->layers[i].size - 1);
> > > + p += n;
> > > + len -= n;
> >
> > What happens if that subtraction causes len to wrap around and become a
> > huge positive unsigned integer?
If you're really concerned about wrapping, use scnprintf.
next prev parent reply other threads:[~2020-09-17 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 2:48 [PATCH v2] EDAC/mc_sysfs: Add missing newlines when printing {max,dimm}_location Xiongfeng Wang
2020-09-16 17:00 ` Borislav Petkov
2020-09-17 11:38 ` Xiongfeng Wang
2020-09-17 15:28 ` Joe Perches [this message]
2020-09-17 16:25 ` Borislav Petkov
2020-09-18 2:37 ` Xiongfeng Wang
2020-09-18 7:12 ` Borislav Petkov
2020-09-18 13:31 ` Joe Perches
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=707865b7ccc9168177940cd4f63cf7cb9ead2d63.camel@perches.com \
--to=joe@perches.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=tony.luck@intel.com \
--cc=wangxiongfeng2@huawei.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