public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xiongfeng Wang <wangxiongfeng2@huawei.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>, Willy Tarreau <w@1wt.eu>
Cc: Dan <dan.carpenter@oracle.com>, Arnd Bergmann <arnd@arndb.de>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] auxdisplay: use correct string length
Date: Tue, 13 Feb 2018 09:19:21 +0800	[thread overview]
Message-ID: <a1034df8-246d-e979-e2ee-2974ae31dde7@huawei.com> (raw)
In-Reply-To: <CANiq72=AeytaT5KBtujTBUkfbNTFFxMPAeToqzmZJOr790R6yw@mail.gmail.com>



On 2018/2/12 20:53, Miguel Ojeda wrote:
> On Tue, Jan 16, 2018 at 10:38 AM, Xiongfeng Wang
> <wangxiongfeng2@huawei.com> wrote:
>> From: Xiongfeng Wang <xiongfeng.wang@linaro.org>
>>
>> gcc-8 reports
>>
>> drivers/auxdisplay/panel.c: In function 'panel_attach':
>> ./include/linux/string.h:245:9: warning: '__builtin_strncpy' specified
>> bound 12 equals destination size [-Wstringop-truncation]
>>
>> We need one less byte or call strlcpy() to make it a nul-terminated
>> string.
>>
>> Signed-off-by: Xiongfeng Wang <xiongfeng.wang@linaro.org>
>> ---
>>  drivers/auxdisplay/panel.c | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/auxdisplay/panel.c b/drivers/auxdisplay/panel.c
>> index ea7869c..d288900 100644
>> --- a/drivers/auxdisplay/panel.c
>> +++ b/drivers/auxdisplay/panel.c
>> @@ -1506,10 +1506,10 @@ static struct logical_input *panel_bind_key(const char *name, const char *press,
>>         key->rise_time = 1;
>>         key->fall_time = 1;
>>
>> -       strncpy(key->u.kbd.press_str, press, sizeof(key->u.kbd.press_str));
>> -       strncpy(key->u.kbd.repeat_str, repeat, sizeof(key->u.kbd.repeat_str));
>> +       strncpy(key->u.kbd.press_str, press, sizeof(key->u.kbd.press_str) - 1);
>> +       strncpy(key->u.kbd.repeat_str, repeat, sizeof(key->u.kbd.repeat_str) - 1);
>>         strncpy(key->u.kbd.release_str, release,
>> -               sizeof(key->u.kbd.release_str));
>> +               sizeof(key->u.kbd.release_str) - 1);
> 
> Are you sure about this patch? `kbd` says "strings can be non null-terminated".
> 
> Willy, maybe those should just be memcpy()s? (unless the remaining
> bytes, if any, must be 0).
Sorry, my apologies. I think I made a mistake. I meant to use strlcpy(), but this
also decrease the destination storage size by one.
I think, if the strings can be non null-terminated,  we can just use memcpy().
This may suppress the gcc warning.

Thanks,
Xiongfeng

> 
> Thanks,
> Miguel
> 
>>         list_add(&key->list, &logical_inputs);
>>         return key;
>>  }
>> --
>> 1.8.3.1
>>
> 
> .
> 

  parent reply	other threads:[~2018-02-13  1:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16  9:38 [PATCH V2] auxdisplay: use correct string length Xiongfeng Wang
2018-02-12 12:53 ` Miguel Ojeda
2018-02-12 17:11   ` Willy Tarreau
2018-02-12 20:42     ` Miguel Ojeda
2018-02-13  1:19   ` Xiongfeng Wang [this message]
2018-02-13  7:23     ` Willy Tarreau
2018-02-13  8:28       ` Arnd Bergmann

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=a1034df8-246d-e979-e2ee-2974ae31dde7@huawei.com \
    --to=wangxiongfeng2@huawei.com \
    --cc=arnd@arndb.de \
    --cc=dan.carpenter@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=w@1wt.eu \
    /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