From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-scsi@vger.kernel.org, target-devel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [patch] target: change sprintf to snprintf
Date: Fri, 18 Jan 2013 11:36:52 -0800 [thread overview]
Message-ID: <1358537812.18551.446.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <20130118130512.GA1634@elgon.mountain>
On Fri, 2013-01-18 at 16:05 +0300, Dan Carpenter wrote:
> "buf" is 128 characters and "vpd->device_identifier" is 256. It makes
> the static checkers complain.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
Applied to target-pending/for-next.
> Probably we should just raise VPD_TMP_BUF_SIZE to 300.
Also bumping up VPD_TMP_BUF_SIZE to 254 to match the usage with
INQUIRY_VPD_DEVICE_IDENTIFIER_LEN sized vpd->device_identifier[] below.
Thanks Dan!
--nab
>
> diff --git a/drivers/target/target_core_transport.c b/drivers/target/target_core_transport.c
> index bd587b7..96b64d5 100644
> --- a/drivers/target/target_core_transport.c
> +++ b/drivers/target/target_core_transport.c
> @@ -907,15 +907,18 @@ int transport_dump_vpd_ident(
>
> switch (vpd->device_identifier_code_set) {
> case 0x01: /* Binary */
> - sprintf(buf, "T10 VPD Binary Device Identifier: %s\n",
> + snprintf(buf, sizeof(buf),
> + "T10 VPD Binary Device Identifier: %s\n",
> &vpd->device_identifier[0]);
> break;
> case 0x02: /* ASCII */
> - sprintf(buf, "T10 VPD ASCII Device Identifier: %s\n",
> + snprintf(buf, sizeof(buf),
> + "T10 VPD ASCII Device Identifier: %s\n",
> &vpd->device_identifier[0]);
> break;
> case 0x03: /* UTF-8 */
> - sprintf(buf, "T10 VPD UTF-8 Device Identifier: %s\n",
> + snprintf(buf, sizeof(buf),
> + "T10 VPD UTF-8 Device Identifier: %s\n",
> &vpd->device_identifier[0]);
> break;
> default:
next prev parent reply other threads:[~2013-01-18 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 13:05 [patch] target: change sprintf to snprintf Dan Carpenter
2013-01-18 19:36 ` Nicholas A. Bellinger [this message]
2013-01-18 21:35 ` Dan Carpenter
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=1358537812.18551.446.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=target-devel@vger.kernel.org \
/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