Re: EIP is at device_shutdown+0x32/0x60


Care to try this:
+ system_kset = kset_create_and_register("system", NULL,
+ &devices_kset->kobj, NULL);

We should not join the kset, only use it as a parent.

Yes, that fixes the problem for me!

Can anyone else verify this?

I confirmed it fixed the problem. :-)

Thanks.


--
Yasunori Goto


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: EIP is at device_shutdown+0x32/0x60
    ... We should not join the kset, only use it as a parent. ... that fixes the problem for me! ... Can anyone else verify this? ...
    (Linux-Kernel)
  • Re: EIP is at device_shutdown+0x32/0x60
    ... Care to try this: ... We should not join the kset, only use it as a parent. ... since this fixes things for me on s390 as well. ...
    (Linux-Kernel)
  • Re: get_device_parent() race bug
    ... kset and then try to create sysfs directory for it. ... see whether the cuse class dir exists. ... kobject_add_internal(): ... device to the parent kobj returned by get_device_parent. ...
    (Linux-Kernel)
  • Re: [RFC] New kobject/kset/ktype documentation and example code
    ... the creator are its ktype, kset, and parent. ... In fact kset, ktype, and parent are optional, right? ... reference tries to access the kobject and crashes. ...
    (Linux-Kernel)
  • [PATCH 02/10] kobject: kerneldoc comment fix
    ... @parent: the parent kobject of this kobject, ... * This function creates a kset structure dynamically and registers it ... + * This function creates a kobject structure dynamically and registers it ...
    (Linux-Kernel)