Re: [PATCH 2.6.10-rc1 2/5] driver-model: bus_recan_devices() locking fix
From: Greg KH
Date: Tue Nov 09 2004 - 19:53:24 EST
On Fri, Nov 05, 2004 at 11:33:37AM -0500, Dmitry Torokhov wrote:
> On Fri, 5 Nov 2004 15:14:39 +0900, Tejun Heo <tj@xxxxxxxxxxx> wrote:
> > Or maybe just adding a @write_lock argument to bus_for_each_*()
> > functions or create a new function named __bus_for_each_*() which
> > takes additional @write_lock argument.
> > However, I don't really think the get_bus/put_bus() calls are
> > necessary there. Unless the caller already has a reference to the
> > bus, we're in trouble anyway. get_bus() cannot synchronize with the
> > last put_bus(), we need outer synchronization to protect that
> > (individual bus drivers are expected to perform the synchronization).
> Yes I think you are right.
> > One thing that bothers me is all the "if (kobject_get(x))" codes.
> > Currently, it doesn't seem to do anything other than checking if x is
> > NULL or not and incrementing the reference count. i.e. the return
> > value only represents if x is NULL or not. I find the codes
> > misleading. It seems like above statement can synchronize get() and
> > the last put() which isn't true. I don't how how the using xchg in
> > kref went, but with preemtion turned on, I don't see how it's gonna
> > change the situation.
> I agree it is somewhat misleading. And even if _get would synchronize
> with _put taht wouldmean that the caller does not have a valid reference
> and the kernel will crash there next time callers uses the object in
> I think we just have lay down the rules that one needs to get a reference
> to an object in the following cases:
> - object creation (first reference)
> - linking some other object to the object in question. Every link to the
> object should increase reference count.
> - before passing object to another thread of execution to guarantee that
> the object will live long enough for both threads.
The rules are defined. See my OLS 2004 paper on krefs for details.
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/