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: <CAN2+FEKvNz1eCUyThPs3qoX+uG__KzTu67egnu-pz7hxmM9Jjw@mail.gmail.com>
Date:	Sun, 5 Oct 2014 18:13:05 -0400
From:	Jason Noakes <jjnoakes@...il.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: kobject_init and the zeroed-out-memory requirement

> No driver should be working with "raw" kobjects.

I don't agree, but it's irrelevant. If the functions are exported and
documented, the documentation should be complete.

> kobject_init() has been there for a very long time, and yes, we don't
> always have the best naming scheme in the kernel, that comes from
> evolution over the years.

If you ever want to rename it, drop me a line. I'll submit the patch
for that too :)

> Care to resend this in a format I can apply it in (i.e. without this
> discussion above the patch forcing me to edit the changelog)?

Sure.

-- 
~~ Jason J. Noakes
~~ jjnoakes@...il.com
--
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/