public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch v2] cx231xx: card->driver "Conexant cx231xx Audio" too long
Date: Mon, 22 Mar 2010 17:21:22 +0000	[thread overview]
Message-ID: <s5hbpegw9v1.wl%tiwai@suse.de> (raw)
In-Reply-To: <20100322153909.GC23411@bicker>

At Mon, 22 Mar 2010 18:18:04 +0100,
walter harms wrote:
> 
> 
> 
> Takashi Iwai schrieb:
> > 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
> > 
> > 
> > Takashi
> > --
> 
> 
> did i miss something ?

Yes :)

> why not change  card->driver int char * ? a simple card->driver="name"
> would solve the problem.

The length is fixed because it's used for ioctl.


Takashi

  parent reply	other threads:[~2010-03-22 17:21 UTC|newest]

Thread overview: 12+ 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     ` [patch v2] cx231xx: card->driver "Conexant cx231xx Audio" too Joe Perches
2010-03-22 16:04       ` [patch v2] cx231xx: card->driver "Conexant cx231xx Audio" too long Takashi Iwai
2010-03-22 16:54         ` [patch v2] cx231xx: card->driver "Conexant cx231xx Audio" too Dan Carpenter
2010-03-22 16:57           ` [patch v2] cx231xx: card->driver "Conexant cx231xx Audio" too long Takashi Iwai
2010-03-23 16:43         ` [patch v2] cx231xx: card->driver "Conexant cx231xx Audio" too Marcin Slusarz
2010-03-22 17:18     ` walter harms
2010-03-22 17:21     ` Takashi Iwai [this message]
2010-03-22 17:50     ` walter harms
2010-03-23  6:59     ` [patch v2] cx231xx: card->driver "Conexant cx231xx Audio" too long 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=s5hbpegw9v1.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=kernel-janitors@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