Re: [OOPS/HACK] atmel_cs and the latest changes in sysfs/symlink.c

Greg KH
2004-04-25T02:50:28Z

On Sat, Apr 24, 2004 at 01:44:04AM -0500, Dmitry Torokhov wrote:
> On Friday 23 April 2004 01:03 pm, Greg KH wrote:
> > On Fri, Apr 23, 2004 at 10:19:53AM -0700, Greg KH wrote:
> > > On Fri, Apr 23, 2004 at 08:31:11AM -0700, Greg KH wrote:
> > > >
> > > > No, we need to oops, as that's a real bug. Can you post the whole oops
> > > > that was generated with this usb problem? I can't seem to duplicate
> > > > this here.
> > >
> > > Nevermind I dug up a device here that causes this problem. I'll track
> > > it down...
> >
> > Ok, here's a patch that fixes it for me. I was waiting for a good
> > reason to finally get rid of this fake usb_interface structure, and now
> > I have it :)
> >
>
> Yes, it does fix it for me, thanks a lot!
> Now if somebody could fix the following oops...

When does that oops happen? With my patch applied? Are you yanking out
a device that currently has a userspace progam attached to it? What
kind of device is it?

Hm, this might solve the problem, can you try the patch below? It's on
top of my previous patch.

thanks,

greg k-h

--- a/drivers/usb/input/hiddev.c Fri Apr 23 10:59:52 2004
+++ b/drivers/usb/input/hiddev.c Sat Apr 24 19:46:29 2004
@@ -233,8 +233,8 @@
static struct usb_class_driver hiddev_class;
static void hiddev_cleanup(struct hiddev *hiddev)
{
- usb_deregister_dev(hiddev->hid->intf, &hiddev_class);
hiddev_table[hiddev->minor] = NULL;
+ usb_deregister_dev(hiddev->hid->intf, &hiddev_class);
kfree(hiddev);
}