From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Peter Wu <peter@lekensteyn.nl>
Cc: Jiri Kosina <jkosina@suse.cz>,
Nestor Lopez Casado <nlopezcasad@logitech.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] HID: logitech-hidpp: do not return the name length
Date: Wed, 10 Dec 2014 18:01:52 -0500 [thread overview]
Message-ID: <20141210230152.GC4861@mail.corp.redhat.com> (raw)
In-Reply-To: <4561294.qneDZ51mgu@al>
On Dec 10 2014 or thereabouts, Peter Wu wrote:
> On Wednesday 10 December 2014 17:21:09 Benjamin Tissoires wrote:
> > We do not make any use of the actual name length get through
> > hidpp_get_device_name().
> >
> > We can drop the extra code and simplify the API a bit.
> >
> > Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> >
> > ---
> > drivers/hid/hid-logitech-hidpp.c | 10 +++-------
> > 1 file changed, 3 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-logitech-hidpp.c
> > index 1a6395d..3846305 100644
> > --- a/drivers/hid/hid-logitech-hidpp.c
> > +++ b/drivers/hid/hid-logitech-hidpp.c
> > @@ -461,7 +461,7 @@ static int hidpp_devicenametype_get_device_name(struct hidpp_device *hidpp,
> > return count;
> > }
> >
> > -static char *hidpp_get_device_name(struct hidpp_device *hidpp, u8 *name_length)
> > +static char *hidpp_get_device_name(struct hidpp_device *hidpp)
> > {
> > u8 feature_type;
> > u8 feature_index;
> > @@ -484,7 +484,6 @@ static char *hidpp_get_device_name(struct hidpp_device *hidpp, u8 *name_length)
> > if (!name)
> > goto out_err;
> >
> > - *name_length = __name_length + 1;
> > while (index < __name_length)
> > index += hidpp_devicenametype_get_device_name(hidpp,
> > feature_index, index, name + index,
>
> hidpp_devicenametype_get_device_name can return a non-positive value if
> the USB device is unplugged at the wrong time, or if a malicious device
> is attached (and 0 is returned). An infinite loop is the result.
Oh, yes, you are definitively right.
>
> Can you apply this change in the patch or should I send you a separate
> one?
Feel free to send your patch directly to the list.
>
> while (index < __name_length) {
> ret = hidpp_devicenametype_get_device_name(hidpp,
> feature_index, index, name + index,
> __name_length - index);
> if (ret <= 0) {
> kfree(name);
> return NULL;
> }
> index += ret;
> }
>
> > @@ -493,7 +492,6 @@ static char *hidpp_get_device_name(struct hidpp_device *hidpp, u8 *name_length)
> > return name;
> >
> > out_err:
> > - *name_length = 0;
> > return NULL;
>
> What about dropping the label out_err here and returning NULL in the
> previous places?
Yep, good idea. You can either send a patch for that if you want to take
credits, or I can send a v2. It's up to you.
Cheers,
Benjamin
>
> > }
> >
> > @@ -989,7 +987,6 @@ static void hidpp_overwrite_name(struct hid_device *hdev, bool use_unifying)
> > {
> > struct hidpp_device *hidpp = hid_get_drvdata(hdev);
> > char *name;
> > - u8 name_length;
> >
> > if (use_unifying)
> > /*
> > @@ -999,7 +996,7 @@ static void hidpp_overwrite_name(struct hid_device *hdev, bool use_unifying)
> > */
> > name = hidpp_get_unifying_name(hidpp);
> > else
> > - name = hidpp_get_device_name(hidpp, &name_length);
> > + name = hidpp_get_device_name(hidpp);
> >
> > if (!name)
> > hid_err(hdev, "unable to retrieve the name of the device");
> > @@ -1053,7 +1050,6 @@ static void hidpp_connect_event(struct hidpp_device *hidpp)
> > bool connected = atomic_read(&hidpp->connected);
> > struct input_dev *input;
> > char *name, *devm_name;
> > - u8 name_length;
> >
> > if (hidpp->quirks & HIDPP_QUIRK_CLASS_WTP)
> > wtp_connect(hdev, connected);
> > @@ -1080,7 +1076,7 @@ static void hidpp_connect_event(struct hidpp_device *hidpp)
> > return;
> > }
> >
> > - name = hidpp_get_device_name(hidpp, &name_length);
> > + name = hidpp_get_device_name(hidpp);
> > if (!name) {
> > hid_err(hdev, "unable to retrieve the name of the device");
> > } else {
> >
>
next prev parent reply other threads:[~2014-12-10 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 22:21 [PATCH 1/2] HID: logitech-hidpp: do not return the name length Benjamin Tissoires
2014-12-10 22:21 ` [PATCH 2/2] HID: logitech-hidpp: prefix the name with Logitech Benjamin Tissoires
2014-12-10 23:01 ` Peter Wu
2014-12-10 23:17 ` Benjamin Tissoires
2014-12-11 13:24 ` Peter Wu
2014-12-11 15:50 ` Benjamin Tissoires
2014-12-10 22:53 ` [PATCH 1/2] HID: logitech-hidpp: do not return the name length Peter Wu
2014-12-10 23:01 ` Benjamin Tissoires [this message]
2014-12-11 0:06 ` Peter Wu
2014-12-11 1:33 ` Benjamin Tissoires
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=20141210230152.GC4861@mail.corp.redhat.com \
--to=benjamin.tissoires@redhat.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nlopezcasad@logitech.com \
--cc=peter.hutterer@who-t.net \
--cc=peter@lekensteyn.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.