Re: [RFC] kobject/kset/ktype documentation and example code updated

[Randy Dunlap <randy.dunlap@oracle.com>]

Greg KH wrote:
> On Thu, Dec 20, 2007 at 02:29:52PM -0800, Randy Dunlap wrote:
> > On Thu, 20 Dec 2007 14:12:52 -0800 Greg KH wrote:
> >
> > > On Thu, Dec 20, 2007 at 02:06:59PM -0800, Randy Dunlap wrote:
> > > > On Thu, 20 Dec 2007 13:27:00 -0800 Greg KH wrote:
> > > > > On Wed, Dec 19, 2007 at 10:32:06PM -0800, Randy Dunlap wrote:
> > > > > > On Wed, 19 Dec 2007 16:30:31 -0800 Greg KH wrote:
> > > > > > >     int kobject_uevent(struct kobject *kobj, enum kobject_action action);
> > > > > > >
> > > > > > > Use the KOBJ_ADD action for when the kobject is first added to the kernel.
> > > > > > > This should be done only after any attributes or children of the kobject
> > > > > > > have been initialized properly, as userspace will instantly start to look
> > > > > > 		s/will/may/
> > > > > No, it's usually a "will", as udev is damm fast these days :)
> > > > But that's the point.  It assumes that udev is being used.  :(
> > > Yes, kernel developers need to be aware that udev _will_ be used, you
> > > can not do things that will assume it is not running.
> > so are you saying that udev is required now?
> > I missed that information somehow/somewhere.
>
> No, not at all, it's not required.
>
> Just that if you are creating kobjects, you need to be aware that there
> are programs out there, like udev[1], that expect once the kobject is
> announced, to have all of the attributes present at the same time.
>
> Does that explain it better?

Yes.  Thanks.

> thanks,
>
> greg k-h
>
> [1] There are at least 2 other programs like udev used by distros these
> days, udev is not the only player in this area anymore.


--
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/