From: Takashi Iwai <tiwai@suse.de>
To: "Oleksandr Andrushchenko" <andr2000@gmail.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Oleksandr Andrushchenko" <oleksandr_andrushchenko@epam.com>,
"Jaroslav Kysela" <perex@perex.cz>, <alsa-devel@alsa-project.org>,
<xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] [PATCH] ALSA: xen: ensure nul-terminated device name
Date: Tue, 29 May 2018 08:28:26 +0200 [thread overview]
Message-ID: <s5h4lirasc5.wl-tiwai@suse.de> (raw)
In-Reply-To: <2469af3f-df85-fbca-a486-566f9aaa436d@gmail.com>
On Tue, 29 May 2018 07:48:51 +0200,
Oleksandr Andrushchenko wrote:
>
> On 05/28/2018 06:59 PM, Arnd Bergmann wrote:
> > gcc-8 warns that pcm_instance->name is not necessarily terminated correctly
> > if the input is more than 80 characters long or lacks a termination byte
> > itself:
> >
> > In function 'strncpy',
> > inlined from 'cfg_device' at sound/xen/xen_snd_front_cfg.c:399:3,
> > inlined from 'xen_snd_front_cfg_card' at sound/xen/xen_snd_front_cfg.c:509:9:
> > include/linux/string.h:254:9: error: '__builtin_strncpy' specified bound 80 equals destination size [-Werror=stringop-truncation]
> > return __builtin_strncpy(p, q, size);
> >
> > Using strlcpy() instead of strncpy() makes this a bit safer.
> >
> > Fixes: fd3b36045c2c ("ALSA: xen-front: Read sound driver configuration from Xen store")
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > ---
> > sound/xen/xen_snd_front_cfg.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/sound/xen/xen_snd_front_cfg.c b/sound/xen/xen_snd_front_cfg.c
> > index 38c7e1eefbb9..684b5f1d51ac 100644
> > --- a/sound/xen/xen_snd_front_cfg.c
> > +++ b/sound/xen/xen_snd_front_cfg.c
> > @@ -396,7 +396,7 @@ static int cfg_device(struct xen_snd_front_info *front_info,
> > str = xenbus_read(XBT_NIL, device_path,
> > XENSND_FIELD_DEVICE_NAME, NULL);
> > if (!IS_ERR(str)) {
> > - strncpy(pcm_instance->name, str, sizeof(pcm_instance->name));
> > + strlcpy(pcm_instance->name, str, sizeof(pcm_instance->name));
> > kfree(str);
> > }
> >
> Thank you for your patch,
> Reviewed-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2018-05-29 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 15:59 Arnd Bergmann
2018-05-29 5:48 ` [alsa-devel] " Oleksandr Andrushchenko
2018-05-29 6:28 ` Takashi Iwai [this message]
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=s5h4lirasc5.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andr2000@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--cc=perex@perex.cz \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®