From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcin Slusarz Date: Tue, 23 Mar 2010 16:43:23 +0000 Subject: Re: [patch v2] cx231xx: card->driver "Conexant cx231xx Audio" too Message-Id: <20100323164323.GA2841@joi.lan> List-Id: References: <20100319114957.GQ5331@bicker> <20100322153909.GC23411@bicker> <1269272627.22616.35.camel@Joe-Laptop.home> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Takashi Iwai Cc: Joe Perches , Dan Carpenter , Mauro Carvalho Chehab , Srinivasa Deevi , linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org 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