From: Dan Carpenter <dan.carpenter@oracle.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kernel-janitors@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
virtualization@lists.linux-foundation.org
Subject: [patch v2] virtio_console: silence a static checker warning
Date: Fri, 8 May 2015 12:16:25 +0300 [thread overview]
Message-ID: <20150508091624.GS14154@mwanda> (raw)
In-Reply-To: <20150508063118.GA6361@grmbl.mre>
My static checker complains that this sprintf() can overflow but really
it can't. Just silence the warning by using snprintf().
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
---
v2: the overflow is not possible so just leave the buffer size alone and
silence the warning with snprintf().
diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c
index 50754d20..8283989 100644
--- a/drivers/char/virtio_console.c
+++ b/drivers/char/virtio_console.c
@@ -1492,8 +1492,8 @@ static int add_port(struct ports_device *portdev, u32 id)
* Finally, create the debugfs file that we can use to
* inspect a port's state at any time
*/
- sprintf(debugfs_name, "vport%up%u",
- port->portdev->vdev->index, id);
+ snprintf(debugfs_name, sizeof(debugfs_name), "vport%up%u",
+ port->portdev->vdev->index, id);
port->debugfs_file = debugfs_create_file(debugfs_name, 0444,
pdrvdata.debugfs_dir,
port,
next prev parent reply other threads:[~2015-05-08 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150508061902.GA14769@mwanda>
2015-05-08 6:31 ` [patch] virtio_console: use snprintf() for safety Amit Shah
2015-05-08 9:16 ` Dan Carpenter [this message]
2015-05-08 9:29 ` [patch v2] virtio_console: silence a static checker warning Amit Shah
2015-05-08 9:30 ` walter harms
[not found] ` <554C8221.9070304@bfs.de>
2015-05-08 9:47 ` Dan Carpenter
2015-05-08 9:56 ` Amit Shah
[not found] ` <20150508095616.GB5527@grmbl.mre>
2015-05-08 11:13 ` walter harms
[not found] ` <554C9A52.4030707@bfs.de>
2015-05-08 12:18 ` 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=20150508091624.GS14154@mwanda \
--to=dan.carpenter@oracle.com \
--cc=amit.shah@redhat.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).