Re: [PATCH, RFC] sysfs: only allow one scheduled removal callbackper kobj

[Cornelia Huck]

On Wed, 11 Mar 2009 08:32:28 -0700,
Greg KH <gregkh@xxxxxxx> wrote:

> Why can't you use device_unregister()?  Or, you could use device_del(),
> which lets you rely on the fact that the device structure is still
> around for a bit, but it will disappear from sysfs.  Just don't forget
> to do the final put_device() on it to free the memory and "really"
> release it.
> 
> Or am I missing something else here?

You can't unregister a device from one of its attribute callbacks, it
locks up in sysfs (removing the sysfs dir waits for all active
references to be dropped, but the reference obtained before calling
->store won't be dropped until after ->store returned...)
device_schedule_callback() was introduced to solve exactly that problem.

(For the original oops, I'd rather solve the problem by making sure the
caller doesn't trigger removal several times - should probably be less
code than the proposed patch?)
--
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/