[lkml]   [2003]   [Jan]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: kobject_init() sets kobj->subsys wrong?

Hi Matt.

On Sat, 4 Jan 2003, Matt Domsch wrote:

> > Your recent patch creating find_bus("scsi") always returns NULL. I see
> > that's because bus_subsys.list is empty.
> In kobject_add(), with kobj->subsys = NULL, this kobject (embedded inside
> struct subsystem embedded inside struct bus_type) never gets added to
> either it's parent's list, nor to the (NULL) subsystem's list. It appears
> that the object can be on either a parent's list or a subsystem's list,
> but not both, by virtue of there being only one struct list_head entry in
> struct kobject.

Actually, the objects are always placed on their subsystem's list, never
their parent's. An object's parent is only used to determine the location
to insert the object. This gives the subsystem the ability to maintain an
ordered list of all objects registered with it, even when the objects
compose an arbitrarily deep hierarchy.

This is docuemented somewhere, but I'll be sure to add a comment to
kobject_add() explaining this.

> 1) in bus_register(), don't set bus->subsys.parent = &bus_subsys, instead
> set bus->subsys.kobj.subsys = &bus_subsys. I did this, and now find_bus()
> works as expected, but now the busses created don't have parents unless
> they're specified prior to calling bus_register(), so this doesn't seem
> quite right.

This is correct. Also in kobject_add(), orphan objects are adopted by
the subsystem they belong to.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:32    [W:0.026 / U:1.832 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site