From: Dave Jiang <dave.jiang@intel.com>
To: Dan Carpenter <dan.carpenter@oracle.com>,
Jon Mason <jdmason@kudzu.us>,
Logan Gunthorpe <logang@deltatee.com>
Cc: Allen Hubbe <Allen.Hubbe@emc.com>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-ntb@googlegroups.com, kernel-janitors@vger.kernel.org
Subject: Re: [patch] ntb_perf: potential info leak in debugfs
Date: Fri, 14 Oct 2016 10:07:13 -0700 [thread overview]
Message-ID: <2df67889-a7d5-2313-2828-3457115fbcfa@intel.com> (raw)
In-Reply-To: <20161014073418.GD15168@mwanda>
On 10/14/2016 12:34 AM, Dan Carpenter wrote:
> This is a static checker warning, not something I'm desperately
> concerned about. But snprintf() returns the number of bytes that
> would have been copied if there were space. We really care about the
> number of bytes that actually were copied so we should use scnprintf()
> instead.
>
> It probably won't overrun, and in that case we may as well just use
> sprintf() but these sorts of things make static checkers and code
> reviewers happier.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Acked-by: Dave Jiang <dave.jiang@intel.com>
>
> diff --git a/drivers/ntb/test/ntb_perf.c b/drivers/ntb/test/ntb_perf.c
> index 6a50f20..2d9ca58 100644
> --- a/drivers/ntb/test/ntb_perf.c
> +++ b/drivers/ntb/test/ntb_perf.c
> @@ -589,7 +589,7 @@ static ssize_t debugfs_run_read(struct file *filp, char __user *ubuf,
> return -ENOMEM;
>
> if (mutex_is_locked(&perf->run_mutex)) {
> - out_off = snprintf(buf, 64, "running\n");
> + out_off = scnprintf(buf, 64, "running\n");
> goto read_from_buf;
> }
>
> @@ -600,14 +600,14 @@ static ssize_t debugfs_run_read(struct file *filp, char __user *ubuf,
> break;
>
> if (pctx->status) {
> - out_off += snprintf(buf + out_off, 1024 - out_off,
> + out_off += scnprintf(buf + out_off, 1024 - out_off,
> "%d: error %d\n", i,
> pctx->status);
> continue;
> }
>
> rate = div64_u64(pctx->copied, pctx->diff_us);
> - out_off += snprintf(buf + out_off, 1024 - out_off,
> + out_off += scnprintf(buf + out_off, 1024 - out_off,
> "%d: copied %llu bytes in %llu usecs, %llu MBytes/s\n",
> i, pctx->copied, pctx->diff_us, rate);
> }
>
next prev parent reply other threads:[~2016-10-14 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 7:34 [patch] ntb_perf: potential info leak in debugfs Dan Carpenter
2016-10-14 17:07 ` Dave Jiang [this message]
2016-11-01 20:35 ` Jon Mason
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=2df67889-a7d5-2313-2828-3457115fbcfa@intel.com \
--to=dave.jiang@intel.com \
--cc=Allen.Hubbe@emc.com \
--cc=arnd@arndb.de \
--cc=dan.carpenter@oracle.com \
--cc=jdmason@kudzu.us \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=logang@deltatee.com \
--cc=sudipm.mukherjee@gmail.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