From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Joe Perches <joe@perches.com>, Dan Carpenter <error27@gmail.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Srinivasa Deevi <srinivasa.deevi@conexant.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [patch v2] cx231xx: card->driver "Conexant cx231xx Audio" too long
Date: Tue, 23 Mar 2010 17:43:23 +0100 [thread overview]
Message-ID: <20100323164323.GA2841@joi.lan> (raw)
In-Reply-To: <s5h39zsxryw.wl%tiwai@suse.de>
On Mon, Mar 22, 2010 at 05:04:55PM +0100, Takashi Iwai wrote:
> At Mon, 22 Mar 2010 08:43:47 -0700,
> Joe Perches wrote:
> >
> > On Mon, 2010-03-22 at 18:39 +0300, Dan Carpenter wrote:
> > > card->driver is 15 characters and a NULL, the original code could
> > > cause a buffer overflow.
> >
> > > In version 2, I used a better name that Takashi Iwai suggested.
> >
> > Perhaps it's better to use strncpy as well.
>
> strlcpy() would be safer :)
>
> But, in such a case, we want rather that the error is notified at
> build time.
>
> Maybe a macro like below would be helpful to catch such bugs?
>
> #define COPY_STRING(buf, src) \
> do { \
> if (__builtin_constant_p(src)) \
> BUILD_BUG_ON(strlen(src) >= sizeof(buf)); \
> strcpy(buf, src); \
> } while (0)
>
> and used like:
>
> struct foo {
> char foo[5];
> } x;
>
> COPY_STRING(x.foo, "OK"); // OK
> COPY_STRING(x.foo, "1234567890"); // NG
why not define strcpy this way?
Marcin
next prev parent reply other threads:[~2010-03-23 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 11:49 [patch] cx231xx: card->driver "Conexant cx231xx Audio" too long Dan Carpenter
2010-03-22 14:46 ` Takashi Iwai
2010-03-22 15:39 ` [patch v2] " Dan Carpenter
2010-03-22 15:43 ` Joe Perches
2010-03-22 16:04 ` Takashi Iwai
2010-03-22 16:54 ` Dan Carpenter
2010-03-22 16:57 ` Takashi Iwai
2010-03-23 16:43 ` Marcin Slusarz [this message]
2010-03-23 6:59 ` Takashi Iwai
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=20100323164323.GA2841@joi.lan \
--to=marcin.slusarz@gmail.com \
--cc=error27@gmail.com \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=srinivasa.deevi@conexant.com \
--cc=tiwai@suse.de \
/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