On Mon, Sep 30, 2013 at 10:53:46PM -0700, Bjorn Helgaas wrote:
> I think the current kobject delayed release is too aggressive,
I don't agree with that statement, but the rest of the sentence I do:
> in the
> sense that even after we've released all references, the object can
> still be in sysfs, which causes future creates to fail. E.g., this
> fails:
>
> kset = kset_create_and_add("kobj_test", NULL, NULL);
> kset_unregister(kset);
> kset = kset_create_and_add("kobj_test", NULL, NULL); // FAILS
>
> when I think it should succeed. We don't have a way for the caller to
> determine when it's safe to do the second kset_create_and_add().
The reason this happens is that for some reason I can't fathom, the
sysfs cleanup is done when the release function is called, not when
the object is unregistered.
I can see why that's done - it is so that when a kobject is unregistered,
its sysfs entry hangs around until all the children have gone (and hence
its reference count then hits zero.)
> After we release all references, I think it's OK for the kobject
> itself to continue to exist, i.e., we can delay calling t->release().
> But it should be impossible to find a kobject with refcount == 0 via
> sysfs, so we should be able to create a new one with the same name.
>
> In terms of code, I'm suggesting something like the following:
I think I can give you an ack for this - it looks sensible enough, and
should still have the intended debugging behaviour. I haven't tested
it though.
Acked-by: Russell King <rmk+kernel@xxxxxxxxxxxxxxxx>
Thanks Bjorn.
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
