linux-kernel - Re: kobject_init and the zeroed-out-memory requirement

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]

Message-ID: <20141005232457.GA22525@kroah.com>
Date:	Sun, 5 Oct 2014 16:24:57 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Jason Noakes <jjnoakes@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: kobject_init and the zeroed-out-memory requirement

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.

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/