From: Henk Martijn <h.h.martijn@gmail.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
Greg KH <gregkh@suse.de>, Jiri Kosina <jkosina@suse.cz>
Subject: Re: [patch]fix usbhid using GFP_KERNEL in interrupt
Date: Mon, 21 Sep 2009 22:33:53 +0200 [thread overview]
Message-ID: <4AB7E331.8050209@gmail.com> (raw)
In-Reply-To: <200909212225.48513.oliver@neukum.org>
Oliver Neukum wrote:
> hid:usbhid: fix wrong use of GFP_KERNEL
>
> hid_input_report() must be told it is called in interrupt context
>
> Signed-off-by: Oliver Neukum <oliver@neukum.org>
>
> Hi Jiri, Greg,
>
> this should go into the current tree and the stable tree.
Stable? Interestingly I did not have any problems with 2.6.31......
/Henk
>
> Regards
> Oliver
>
> --
> commit ca5c4a1397d1a1c0d1074f4d8922630fdd732780
> Author: Oliver Neukum <oliver@neukum.org>
> Date: Mon Sep 21 22:02:01 2009 +0200
>
> hid:usbhid: fix wrong use of GFP_KERNEL
>
> hid_input_report() must be told it is called in interrupt context
>
> diff --git a/drivers/hid/usbhid/hid-core.c b/drivers/hid/usbhid/hid-core.c
> index 1b0e07a..ab2869d 100644
> --- a/drivers/hid/usbhid/hid-core.c
> +++ b/drivers/hid/usbhid/hid-core.c
> @@ -455,7 +455,7 @@ static void hid_ctrl(struct urb *urb)
> if (usbhid->ctrl[usbhid->ctrltail].dir == USB_DIR_IN)
> hid_input_report(urb->context,
> usbhid->ctrl[usbhid->ctrltail].report->type,
> - urb->transfer_buffer, urb->actual_length, 0);
> + urb->transfer_buffer, urb->actual_length, 1);
> break;
> case -ESHUTDOWN: /* unplug */
> unplug = 1;
>
>
next prev parent reply other threads:[~2009-09-21 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 20:25 [patch]fix usbhid using GFP_KERNEL in interrupt Oliver Neukum
2009-09-21 20:33 ` Henk Martijn [this message]
2009-09-21 20:37 ` Oliver Neukum
2009-09-21 21:42 ` 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=4AB7E331.8050209@gmail.com \
--to=h.h.martijn@gmail.com \
--cc=gregkh@suse.de \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.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