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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 20 Dec 2007 14:12:52 -0800
From:	Greg KH <greg@...ah.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	linux-kernel@...r.kernel.org, Kay Sievers <kay.sievers@...y.org>,
	Alan Stern <stern@...land.harvard.edu>,
	Jonathan Corbet <corbet@....net>
Subject: Re: [RFC] kobject/kset/ktype documentation and example code updated

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.

> Who is your spell checker?

vim :)

thanks,

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