From: Jesper Juhl <jesper.juhl@gmail.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: vojtech@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: Fw: Oops in hidinput_hid_event
Date: Tue, 19 Jul 2005 03:31:12 +0200 [thread overview]
Message-ID: <9a874849050718183175bc08d4@mail.gmail.com> (raw)
In-Reply-To: <20050718141637.074c6f70.zaitcev@redhat.com>
On 7/18/05, Pete Zaitcev <zaitcev@redhat.com> wrote:
> I think this patch is rather obvious, so maybe I should ask Andrew to
> apply it to -mm for now, to get some testing. Would that help to verify
> it for acceptance?
>
> -- Pete
>
> Begin forwarded message:
>
> Date: Tue, 28 Jun 2005 15:00:23 -0700
> From: Pete Zaitcev <zaitcev@redhat.com>
> To: vojtech@suse.cz
> Cc: zaitcev@redhat.com, linux-usb-devel@lists.sourceforge.net
> Subject: Oops in hidinput_hid_event
>
> Hi, Vojtech:
>
> Someone reported a bug in Fedora, which runs a largely unmodified upstream
> kernel in this area. Whenever the user hits a key which switches LED,
> the system oopses. Here's a trace:
>
> Unable to handle kernel NULL pointer dereference at virtual address 000000c8
> EFLAGS: 00010006 (2.6.11-1.1369_FC4smp)
> EIP is at hidinput_hid_event+0x2d/0x292
> Call Trace:
> [<c02872e0>] hid_process_event+0x57/0x5f
> [<c028758a>] hid_input_field+0x2a2/0x2ac
> [<c0287632>] hid_input_report+0x9e/0xb8
> [<c0287f62>] hid_ctrl+0x14c/0x151
> [<e0a21060>] uhci_destroy_urb_priv+0xb5/0x10a [uhci_hcd]
> [<c027dab5>] usb_hcd_giveback_urb+0x24/0x67
> [<e0a22360>] uhci_finish_urb+0x2d/0x38 [uhci_hcd]
> [<e0a223af>] uhci_finish_completion+0x44/0x56 [uhci_hcd]
> [<e0a224a2>] uhci_scan_schedule+0xaa/0x13a [uhci_hcd]
> [<c023413d>] i8042_interrupt+0x121/0x234
> [<e0a226d0>] uhci_irq+0x47/0x10d [uhci_hcd]
>
> Full trace at
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=160709
>
> Any ideas?
>
> By the way, it seems that I see a bug in hidinput_hid_event.
> The check for NULL can never work, becaue &hidinput->input
> is nonzero at all times. How about this?
>
> --- linux-2.6.12/drivers/usb/input/hid-input.c 2005-06-21 12:58:47.000000000 -0700
> +++ linux-2.6.12-lem/drivers/usb/input/hid-input.c 2005-06-28 14:57:22.000000000 -0700
> @@ -397,11 +397,12 @@
>
> void hidinput_hid_event(struct hid_device *hid, struct hid_field *field, struct hid_usage *usage, __s32 value, struct pt_regs *regs)
> {
> - struct input_dev *input = &field->hidinput->input;
> + struct input_dev *input;
> int *quirks = &hid->quirks;
>
> - if (!input)
> + if (!field->hidinput)
How about
if (!field || !field->hdinput)
instead?
> return;
> + input = &field->hidinput->input;
Add a
if (!input)
return;
check here?
>
> input_regs(input, regs);
>
>
> -- Pete
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-07-19 1:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 21:16 Fw: Oops in hidinput_hid_event Pete Zaitcev
2005-07-19 1:31 ` Jesper Juhl [this message]
2005-07-19 1:34 ` Jesper Juhl
2005-07-19 7:17 ` Pete Zaitcev
2005-07-19 13:30 ` Vojtech Pavlik
2005-07-26 14:11 ` Sergey Vlasov
2005-07-26 3:52 ` Andrew Morton
2005-07-26 4:13 ` Pete Zaitcev
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=9a874849050718183175bc08d4@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
--cc=zaitcev@redhat.com \
/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