Re: [PATCH 25/20] sysfs: Only support removing emtpy sysfs directories.
From: Alan Stern
Date: Wed May 27 2009 - 14:08:20 EST
On Wed, 27 May 2009, James Bottomley wrote:
> By refcount, I mean count of underlying devices.
Does that mean only registered devices, or does it include devices
which are unregistered but not yet released?
> > > The
> > > problem you're complaining about is that the device ref on the target
> > > may take a long time to release, so we can't key the del event on the
> > > refcount going to zero, which is what we do today.
> > Maybe we should be talking about two separate refcounts: a normal
> > get_device/put_device kref counter for the target's lifetime, and a
> > visibility counter (one for each child device and one overall) which
> > keys the del event and must go to 0 before the host removal finishes.
> Um, well, that's roughly how I said we'd have to fix all of this in the
> email to hannes ... it would be much easier if we could make a del'd
> device visible,
I don't follow. Why would you want to delete a target before the host
is removed and then make it visible again later? Because it doesn't
have any underlying devices at the moment but may gain some later on?
If that's the case, why not delete the target when there are no more
registered devices beneath it and then create a new target structure
when a new device appears?
> but now we have to have different behaviours depending
> on whether the host is going away or not.
Yes, one does get the feeling that we're going around in circles...
Okay. So now I have made two proposals. One is to delete targets and
create new ones as needed. The other is to keep a target hanging
around, even if there are no underlying devices, until the host is
removed. This can be implemented easily by making the counter
represent the number of registered devices plus one for the host.
P.S.: If the counter is made to refer to registered devices, as opposed
to un-released devices, would there ever be a situation where you want
to delete a target in a non-process context?
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/