linux-kernel - Re: [PATCH] driver core: implement uevent suppress in kobject(v1)

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:	Mon, 2 Mar 2009 18:51:25 +0100
From:	Cornelia Huck <cornelia.huck@...ibm.com>
To:	tom.leiming@...il.com
Cc:	greg@...ah.com, linux-kernel@...r.kernel.org,
	Ming Lei <tom.leiming@...il.com>
Subject: Re: [PATCH] driver core: implement uevent suppress in kobject(v1)

On Sun,  1 Mar 2009 21:10:49 +0800,
tom.leiming@...il.com wrote:

> From: Ming Lei <tom.leiming@...il.com>
> 
> This patch implements uevent suppress in kobject and removes it
> from struct device, based on the following ideas:
> 
> 1,Uevent sending should be one attribute of kobject, so suppressing it
> in kobject layer is more natural than in device layer. By this way,
> we can do it for other objects embedded with kobject.
> 
> 2,It may save several bytes for each instance of struct device.(On my
> omap3(32bit ARM) based box, can save 8bytes per device object)
> 
> This patch also introduces dev_set|get_uevent_suppress() helpers to
> set and query uevent_suppress attribute in case to help kobject
> as private part of struct device in future.

But moving the kobject into an allocated private structure would be
rather broken?

I have no objections to the patch, though, and it worked fine on my
s390 LPAR.

> 
> [This version is against the latest driver-core patch set of Greg,please
> ignore the last version.]
> 
> Signed-off-by: Ming Lei <tom.leiming@...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/