From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Michael Buesch <mb@bu3sch.de>,
linux-usb-devel@lists.sourceforge.net,
linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: [linux-usb-devel] Oops in khubd
Date: Mon, 4 Jun 2007 10:10:00 -0400 [thread overview]
Message-ID: <d120d5000706040710t4640acb2j14a1f24cfe94311b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706041335320.29896@twin.jikos.cz>
Hi,
On 6/4/07, Jiri Kosina <jikos@jikos.cz> wrote:
> This is probably rather related to something in input. Some CCs added and
> original message preserved below.
>
> I think that struct input_dev passed from hidinput_disconnect() should not
> be the corrupted one, as it is dereferenced sooner on the codepath and it
> doesn't go oops.
>
I think this commit should help:
http://git.kernel.org/?p=linux/kernel/git/dtor/input.git;a=commit;h=fe838febd49be7b8013ae433a6424693180333b5
I just asked Linus to pull it so 2.6.22 does not crash so often while
I am fixing locking properly for 2.6.23.
--
Dmitry
prev parent reply other threads:[~2007-06-04 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200706031240.43330.mb@bu3sch.de>
2007-06-04 11:38 ` [linux-usb-devel] Oops in khubd Jiri Kosina
2007-06-04 14:10 ` Dmitry Torokhov [this message]
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=d120d5000706040710t4640acb2j14a1f24cfe94311b@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=jikos@jikos.cz \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mb@bu3sch.de \
/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).