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]

Message-ID: <a8e1da0712192354k3bce177fi3d30b5737c7d7a9e@mail.gmail.com>
Date:	Thu, 20 Dec 2007 15:54:40 +0800
From:	"Dave Young" <hidave.darkstar@...il.com>
To:	"Greg KH" <greg@...ah.com>
Cc:	linux-kernel@...r.kernel.org, "Kay Sievers" <kay.sievers@...y.org>,
	"Alan Stern" <stern@...land.harvard.edu>,
	"Jonathan Corbet" <corbet@....net>,
	"Randy Dunlap" <randy.dunlap@...cle.com>
Subject: Re: [RFC] kobject/kset/ktype documentation and example code updated

On Dec 20, 2007 8:30 AM, Greg KH <greg@...ah.com> wrote:
> Thanks to everyone for your last round of review comments and changes to
> the kobject documentation.
>
> I now have over 130 patches reworking the kset/ktype and kobject apis in
> the kernel tree, and here is the updated documentation and example code
> that shows how things work now.
>
> Things different from the last time around are the kobject_add() and
> kobject_init() functions now take a bunch of required parameters, and
> the kobject cleanup code is much more forgiving.
>
> I want to drop kobject_unregister() but as this patch series is so big
> already, I think it's time to let it bake in -mm and push into 2.6.25
> before attempting it.
[--snip--]

Hi, greg

How about add a kobject_remove function and temporarily keep the
kobject_unregister as below until the 2.6.25:

kobject_unregister(...)
{
       ...
        kobject_remove();
        kobject_uevent();
        ...
}
--
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/