Messages in this thread | | | Date | Sun, 5 Oct 2014 19:09:50 -0700 | From | Guenter Roeck <> | Subject | Re: kobject_init and the zeroed-out-memory requirement |
| |
On Sun, Oct 05, 2014 at 04:24:57PM -0700, Greg KH wrote: > On Sun, Oct 05, 2014 at 06:13:05PM -0400, Jason Noakes wrote: > > > No driver should be working with "raw" kobjects. > > > > I don't agree, but it's irrelevant. > > Not at all. I'd wager that if a driver is messing around with a "raw" > kobject, it is doing something seriously wrong. Of course there are > exceptions, but those are very rare, and exceptions. A driver should be > using the driver core, and the functions and objects provided there, and > provided by the bus it lives on. > > So, have a pointer to some driver code that is calling > kobject_initialize()? I'd love to see it. >
Lots to choose from. In drivers/:
$ git grep kobject_init | wc 65 289 4880 $ git grep kobject_init | grep -v base | wc 62 277 4694 $ git grep kobject_init_and_add | grep -v base | wc 47 232 3698 $ git grep kobject_add | grep -v base | wc 20 111 1486
Guenter
| |