From: Greg KH <greg@kroah.com>
To: Pete Zaitcev <zaitcev@redhat.com>,
Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Oops in make_class_name in 2.6.22.1 on Fedora
Date: Mon, 10 Sep 2007 23:12:26 -0700 [thread overview]
Message-ID: <20070911061226.GB27404@kroah.com> (raw)
In-Reply-To: <20070910202647.24094d57.zaitcev@redhat.com>
On Mon, Sep 10, 2007 at 08:26:47PM -0700, Pete Zaitcev wrote:
> Hi, Greg (and others):
>
> I do not seem to be able to find an answer, sorry.
> Do you happen to remember if this was fixed after 2.6.22.1:
>
> localhost kernel: EIP is at make_class_name+0x27/0x7a
> localhost kernel: [<c05586f1>] class_device_del+0x97/0x119
> localhost kernel: [<c055877b>] class_device_unregister+0x8/0x10
> localhost kernel: [<e08735f4>] __scsi_remove_device+0x1d/0x60 [scsi_mod]
> localhost kernel: [<e08711ae>] scsi_forget_host+0x2d/0x4a [scsi_mod]
> localhost kernel: [<e086c49c>] scsi_remove_host+0x65/0xd5 [scsi_mod]
> localhost kernel: [<e0e76775>] storage_disconnect+0xe/0x16 [usb_storage]
> localhost kernel: [<c056f8b8>] usb_unbind_interface+0x44/0x85
> localhost kernel: [<c0557df7>] __device_release_driver+0x6e/0x8b
>
> Obviously a known bug but all I see is users reporting it. In my case
> it's this:
> https://bugzilla.redhat.com/show_bug.cgi?id=253424
> I saw Alan giving it a try here:
> http://lkml.org/lkml/2007/7/12/259
I think this was a scsi problem that has been fixed, but don't really
remember the exact commit.
Alan, any ideas?
It would probably be good to get this into the next -stable if we can
figure out which patch did fix it.
thanks,
greg k-h
next prev parent reply other threads:[~2007-09-11 6:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 3:26 Pete Zaitcev
2007-09-11 6:12 ` Greg KH [this message]
2007-09-11 9:17 ` Cornelia Huck
2007-09-11 15:11 ` Alan Stern
2007-10-22 22:06 ` Chuck Ebbert
2007-10-30 16:50 ` Alan Stern
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=20070911061226.GB27404@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
--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
all inboxes | Powered by JetHome®