linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Read <pread99999@gmail.com>
To: akpm@osdl.org, linux-kernel@vger.kernel.org
Cc: pread99999@gmail.com
Subject: FIXED: re: PROBLEM: 2.6.15 Oops in USBHID (good news)
Date: Sun, 22 Jan 2006 14:10:38 -0600	[thread overview]
Message-ID: <25ac9de40601221210q143ba21arf5f442f6321b9db8@mail.gmail.com> (raw)

Greetings,

Andrew asked me to test the 2.6.16-rc1 in regards to an Oops I got at
bootup in 2.6.15 a few weeks ago.

The error was due to a null pointer dereferencing in the USB HID code
(drivers/usb/input/pid.c line 262):

OLD (error) code:
struct hid_input *hidinput = list_entry(&hid->inputs, struct hid_input, list);

NEW (fixed) code:
struct hid_input *hidinput = list_entry(hid->inputs.next, struct
hid_input, list);

The code fix is indeed in 2.6.16-rc1 and the Oops on bootup doesn't
happen on my system anymore with 2.6.16-rc1.

The original debug and Oops messages are still available online in
case anyone doesn't have anything more interesting to read... ;-)

http://www.cs.txstate.edu/~patrick/kernel-debug/

Regards,
Patrick

                 reply	other threads:[~2006-01-22 20:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=25ac9de40601221210q143ba21arf5f442f6321b9db8@mail.gmail.com \
    --to=pread99999@gmail.com \
    --cc=akpm@osdl.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).