From: Bart Van Assche <bvanassche@acm.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
hare@kernel.org, jejb@linux.ibm.com, martin.petersen@oracle.com
Cc: hare@suse.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/2] scsi: myrb: Fix a potential string truncation in rebuild_show()
Date: Tue, 12 Dec 2023 12:14:14 -0800 [thread overview]
Message-ID: <dac24fac-57eb-4ca8-b819-fbdc24464d94@acm.org> (raw)
In-Reply-To: <2d3096dd4b1b6e758287e4062e3147c57c007eaa.1702411083.git.christophe.jaillet@wanadoo.fr>
On 12/12/23 10:09, Christophe JAILLET wrote:
> "physical device - not rebuilding\n" is 34 bytes long. When written in
> 'buf' with a limit of 32 bytes, it is truncated.
>
> When building with W=1, it leads to:
> drivers/scsi/myrb.c: In function ‘rebuild_show’:
> drivers/scsi/myrb.c:1906:24: error: ‘physical device - not rebuil...’ directive output truncated writing 33 bytes into a region of size 32 [-Werror=format-truncation=]
> 1906 | return snprintf(buf, 32, "physical device - not rebuilding\n");
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> drivers/scsi/myrb.c:1906:24: note: ‘snprintf’ output 34 bytes into a destination of size 32
>
> Change the allowed size to 64 to fix the issue.
>
> Fixes: 081ff398c56c ("scsi: myrb: Add Mylex RAID controller (block interface)")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> drivers/scsi/myrb.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/scsi/myrb.c b/drivers/scsi/myrb.c
> index ca2e932dd9b7..ca2380d2d6d3 100644
> --- a/drivers/scsi/myrb.c
> +++ b/drivers/scsi/myrb.c
> @@ -1903,15 +1903,15 @@ static ssize_t rebuild_show(struct device *dev,
> unsigned char status;
>
> if (sdev->channel < myrb_logical_channel(sdev->host))
> - return snprintf(buf, 32, "physical device - not rebuilding\n");
> + return snprintf(buf, 64, "physical device - not rebuilding\n");
>
> status = myrb_get_rbld_progress(cb, &rbld_buf);
>
> if (rbld_buf.ldev_num != sdev->id ||
> status != MYRB_STATUS_SUCCESS)
> - return snprintf(buf, 32, "not rebuilding\n");
> + return snprintf(buf, 64, "not rebuilding\n");
>
> - return snprintf(buf, 32, "rebuilding block %u of %u\n",
> + return snprintf(buf, 64, "rebuilding block %u of %u\n",
> rbld_buf.ldev_size - rbld_buf.blocks_left,
> rbld_buf.ldev_size);
> }
Anyone who sees the resulting code without having seen the above patch will
wonder where the magic number '64' comes from. Please use sysfs_emit() instead
of snprintf(buf, 64, ...).
Thanks,
Bart.
next prev parent reply other threads:[~2023-12-12 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 20:09 [PATCH 0/2] scsi: myrb: Fix a potential string truncation Christophe JAILLET
2023-12-12 20:09 ` [PATCH 1/2] scsi: myrb: Fix a potential string truncation in rebuild_show() Christophe JAILLET
2023-12-12 20:14 ` Bart Van Assche [this message]
2023-12-12 20:20 ` Christophe JAILLET
2023-12-12 20:28 ` Bart Van Assche
2023-12-12 20:09 ` [PATCH 2/2] scsi: myrb: Use sysfs_emit() Christophe JAILLET
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=dac24fac-57eb-4ca8-b819-fbdc24464d94@acm.org \
--to=bvanassche@acm.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=hare@kernel.org \
--cc=hare@suse.com \
--cc=jejb@linux.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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
all inboxes | Powered by JetHome®