All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org, zaitcev@redhat.com
Subject: Re: Zeroing the report before setting fields
Date: Mon, 22 Mar 2010 16:22:06 -0600	[thread overview]
Message-ID: <20100322162206.3c1e9b9e@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1003221726320.18642@pobox.suse.cz>

On Mon, 22 Mar 2010 17:30:31 +0100 (CET)
Jiri Kosina <jkosina@suse.cz> wrote:

> >  	if (dir == USB_DIR_OUT) {
> > -		usbhid->ctrl[usbhid->ctrlhead].raw_report = kmalloc(len, GFP_ATOMIC);
> > +		usbhid->ctrl[usbhid->ctrlhead].raw_report = kzalloc(len, GFP_ATOMIC);
> >  		if (!usbhid->ctrl[usbhid->ctrlhead].raw_report) {
> >  			dev_warn(&hid->dev, "control queueing failed\n");

> Frankly, I like the generic aproach more ... if we were to add more 
> low-level transport HID implementations later, I am sure this will be 
> forgotten multiple times :) (as it isn't directly implied by the HID 
> specification, but is rather a workaround for devices that are violating 
> the spec by looking at the bits they shouldn't care about).

You are right, I screwed the pooch on the layering. Sorry.

Still, I do not want to go back to counting of field lengths.
Too many what-ifs.

How about this (I tested it but clearly my tests are limited):

diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 368fbb0..e290bb3 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -940,13 +940,8 @@ static void hid_output_field(struct hid_field *field, __u8 *data)
 	unsigned count = field->report_count;
 	unsigned offset = field->report_offset;
 	unsigned size = field->report_size;
-	unsigned bitsused = offset + count * size;
 	unsigned n;
 
-	/* make sure the unused bits in the last byte are zeros */
-	if (count > 0 && size > 0 && (bitsused % 8) != 0)
-		data[(bitsused-1)/8] &= (1 << (bitsused % 8)) - 1;
-
 	for (n = 0; n < count; n++) {
 		if (field->logical_minimum < 0)	/* signed values */
 			implement(data, offset + n * size, size, s32ton(field->value[n], size));
@@ -966,6 +961,7 @@ void hid_output_report(struct hid_report *report, __u8 *data)
 	if (report->id > 0)
 		*data++ = report->id;
 
+	memset(data, 0, ((report->size - 1) >> 3) + 1);
 	for (n = 0; n < report->maxfield; n++)
 		hid_output_field(report->field[n], data);
 }

Yours,
-- Pete

  reply	other threads:[~2010-03-22 22:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 21:33 Zeroing the report before setting fields Pete Zaitcev
2010-03-05  8:29 ` Dmitry Torokhov
2010-03-09 12:41   ` Jiri Kosina
2010-03-09 23:26     ` Pete Zaitcev
2010-03-13 22:25       ` Jiri Kosina
2010-03-22  5:09         ` Pete Zaitcev
2010-03-22 16:30           ` Jiri Kosina
2010-03-22 22:22             ` Pete Zaitcev [this message]
2010-04-12 16:08               ` 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=20100322162206.3c1e9b9e@redhat.com \
    --to=zaitcev@redhat.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@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 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.