From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
selvin.xavier@broadcom.com, devesh.sharma@broadcom.com,
dledford@redhat.com, leon@kernel.org, colin.king@canonical.com,
roland@purestorage.com, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] RDMA/ocrdma: Fix an off-by-one issue in 'ocrdma_add_stat'
Date: Fri, 17 Apr 2020 14:26:24 +0300 [thread overview]
Message-ID: <20200417112624.GS1163@kadam> (raw)
In-Reply-To: <20200416184754.GZ5100@ziepe.ca>
On Thu, Apr 16, 2020 at 03:47:54PM -0300, Jason Gunthorpe wrote:
> On Thu, Apr 16, 2020 at 04:08:47PM +0300, Dan Carpenter wrote:
> > On Tue, Apr 14, 2020 at 03:34:41PM -0300, Jason Gunthorpe wrote:
> > > The memcpy is still kind of silly right? What about this:
> > >
> > > static int ocrdma_add_stat(char *start, char *pcur, char *name, u64 count)
> > > {
> > > size_t len = (start + OCRDMA_MAX_DBGFS_MEM) - pcur;
> > > int cpy_len;
> > >
> > > cpy_len = snprintf(pcur, len, "%s: %llu\n", name, count);
> > > if (cpy_len >= len || cpy_len < 0) {
> >
> > The kernel version of snprintf() doesn't and will never return
> > negatives. It would cause a huge security headache if it started
> > returning negatives.
>
> Begs the question why it returns an int then :)
People should use "int" as their default type. "int i;". It means
"This is a normal number. Nothing special about it. It's not too high.
It's not defined by hardware requirements." Other types call attention
to themselves, but int is the humble datatype.
regards,
dan carpenter
next prev parent reply other threads:[~2020-04-17 11:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 7:30 [PATCH] RDMA/ocrdma: Fix an off-by-one issue in 'ocrdma_add_stat' Christophe JAILLET
2020-04-14 18:34 ` Jason Gunthorpe
2020-04-16 13:08 ` Dan Carpenter
2020-04-16 18:47 ` Jason Gunthorpe
2020-04-17 11:26 ` Dan Carpenter [this message]
2020-04-17 12:25 ` Jason Gunthorpe
2020-04-17 13:09 ` Dan Carpenter
2020-04-17 13:48 ` Jason Gunthorpe
2020-04-17 15:13 ` Dan Carpenter
2020-04-17 15:56 ` Jason Gunthorpe
2020-04-17 13:28 ` Marion & Christophe JAILLET
2020-04-17 13:50 ` Jason Gunthorpe
2020-04-17 14:39 ` 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=20200417112624.GS1163@kadam \
--to=dan.carpenter@oracle.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=colin.king@canonical.com \
--cc=devesh.sharma@broadcom.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kernel-janitors@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=roland@purestorage.com \
--cc=selvin.xavier@broadcom.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