From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] HID: picolcd: sanity check report size in raw_event() callback
Date: Thu, 28 Aug 2014 07:57:04 +0200 [thread overview]
Message-ID: <20140828075704.3207e228@pluto> (raw)
In-Reply-To: <alpine.LNX.2.00.1408272331250.21233@pobox.suse.cz>
On Wed, 27 Aug 2014 23:32:00 +0200 (CEST) Jiri Kosina wrote:
> On Wed, 27 Aug 2014, Jiri Kosina wrote:
>
> > > Is it worth adding report->id to this hid_warn()?
> > >
> > > A valid device is not expected to ever send >64 bytes reports but in
> > > case a firmware update would do so it would help to know for which
> > > report it was.
> >
> > It definitely wouldn't hurt. Pull request with the original patch is now
> > on its way to Linus though, so let's do this as a followup patch on top
> > once this is merged.
>
> I've just queued the below for 3.18.
Looks good,
Thanks
Bruno
> From: Jiri Kosina <jkosina@suse.cz>
> Subject: [PATCH] HID: picolcd: be more verbose when reporting report size error
>
> picolcd device is not expected to send any report with size larger than 64
> bytes.
>
> If this impossible event happens (sic!), print also a report ID to allow
> for easier debugging.
>
> Suggested-by: Bruno Prémont <bonbons@linux-vserver.org>
> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
> ---
> drivers/hid/hid-picolcd_core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/hid/hid-picolcd_core.c b/drivers/hid/hid-picolcd_core.c
> index 020df3c..c1b29a9 100644
> --- a/drivers/hid/hid-picolcd_core.c
> +++ b/drivers/hid/hid-picolcd_core.c
> @@ -351,8 +351,8 @@ static int picolcd_raw_event(struct hid_device *hdev,
> return 1;
>
> if (size > 64) {
> - hid_warn(hdev, "invalid size value (%d) for picolcd raw event\n",
> - size);
> + hid_warn(hdev, "invalid size value (%d) for picolcd raw event (%d)\n",
> + size, report->id);
> return 0;
> }
>
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-08-28 5:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 7:12 [PATCH 1/2] HID: magicmouse: sanity check report size in raw_event() callback Jiri Kosina
2014-08-27 7:13 ` [PATCH 2/2] HID: picolcd: " Jiri Kosina
2014-08-27 8:13 ` Bruno Prémont
2014-08-27 8:25 ` Jiri Kosina
2014-08-27 21:32 ` Jiri Kosina
2014-08-28 5:57 ` Bruno Prémont [this message]
2014-08-27 13:54 ` [PATCH 1/2] HID: magicmouse: " 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=20140828075704.3207e228@pluto \
--to=bonbons@linux-vserver.org \
--cc=jkosina@suse.cz \
--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).