On Tue, 8 Oct 2002, Alexander Viro wrote:
> Its reference counts mean squat if they are not seen by the code that
> allocates/frees the object struct device is embedded into.
But Al, that's the whole _point_ of having the callback.
Allow the refcounts to be in an embedded entity, and then anybody who gets
the entity (_or_ the embedded thing) will increment the same count.
When the count goes to zero, the embedded thing needs to call the
_embedders_ release function - because the embedded thing doesn't even
know how it got allocated.
Al, this time you're wrong, and the code you're unhappy about going about
it the right way. The reference count _has_ to be held by the lowest-level
thing (because that's the only generic part), yet the actual allocation
and de-allocation is done by the higher levels. Which is why the lower
levels need to know which freeing function to call.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Oct 15 2002 - 22:00:28 EST