From: Laura Abbott <labbott@redhat.com>
To: David Herrmann <dh.herrmann@gmail.com>, linux-input@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, jikos@kernel.org,
benjamin.tissoires@redhat.com, Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] Revert "HID: uhid: use strlcpy() instead of strncpy()"
Date: Wed, 14 Nov 2018 07:40:43 -0800 [thread overview]
Message-ID: <ea944fb3-0cd9-e6e6-5449-faab7c9603c1@redhat.com> (raw)
In-Reply-To: <20181114131642.21425-1-dh.herrmann@gmail.com>
On 11/14/18 5:16 AM, David Herrmann wrote:
> This reverts commit 336fd4f5f25157e9e8bd50e898a1bbcd99eaea46.
>
> Please note that `strlcpy()` does *NOT* do what you think it does.
> strlcpy() *ALWAYS* reads the full input string, regardless of the
> 'length' parameter. That is, if the input is not zero-terminated,
> strlcpy() will *READ* beyond input boundaries. It does this, because it
> always returns the size it *would* copy if the target was big enough,
> not the truncated size it actually copied.
>
> The original code was perfectly fine. The hid device is
> zero-initialized and the strncpy() functions copied up to n-1
> characters. The result is always zero-terminated this way.
>
> This is the third time someone tried to replace strncpy with strlcpy in
> this function, and gets it wrong. I now added a comment that should at
> least make people reconsider.
>
Can we switch to strscpy instead? This will quiet gcc and avoid the
issues with strlcpy.
> Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
> ---
> drivers/hid/uhid.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/hid/uhid.c b/drivers/hid/uhid.c
> index fefedc0b4dc6..0dfdd0ac7120 100644
> --- a/drivers/hid/uhid.c
> +++ b/drivers/hid/uhid.c
> @@ -496,12 +496,13 @@ static int uhid_dev_create2(struct uhid_device *uhid,
> goto err_free;
> }
>
> - len = min(sizeof(hid->name), sizeof(ev->u.create2.name));
> - strlcpy(hid->name, ev->u.create2.name, len);
> - len = min(sizeof(hid->phys), sizeof(ev->u.create2.phys));
> - strlcpy(hid->phys, ev->u.create2.phys, len);
> - len = min(sizeof(hid->uniq), sizeof(ev->u.create2.uniq));
> - strlcpy(hid->uniq, ev->u.create2.uniq, len);
> + /* @hid is zero-initialized, strncpy() is correct, strlcpy() not */
> + len = min(sizeof(hid->name), sizeof(ev->u.create2.name)) - 1;
> + strncpy(hid->name, ev->u.create2.name, len);
> + len = min(sizeof(hid->phys), sizeof(ev->u.create2.phys)) - 1;
> + strncpy(hid->phys, ev->u.create2.phys, len);
> + len = min(sizeof(hid->uniq), sizeof(ev->u.create2.uniq)) - 1;
> + strncpy(hid->uniq, ev->u.create2.uniq, len);
>
> hid->ll_driver = &uhid_hid_driver;
> hid->bus = ev->u.create2.bus;
>
next prev parent reply other threads:[~2018-11-14 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 13:16 [PATCH] Revert "HID: uhid: use strlcpy() instead of strncpy()" David Herrmann
2018-11-14 15:40 ` Laura Abbott [this message]
2018-11-14 23:09 ` Kees Cook
2018-11-15 11:55 ` David Herrmann
2018-11-16 1:10 ` Kees Cook
2018-11-19 13:33 ` Jiri Kosina
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=ea944fb3-0cd9-e6e6-5449-faab7c9603c1@redhat.com \
--to=labbott@redhat.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dh.herrmann@gmail.com \
--cc=jikos@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).