netdev - Re: [patch 1/1][RFC]Handle uevent per namespace

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 24 Nov 2008 16:20:46 +0100
From:	Daniel Lezcano <dlezcano@...ibm.com>
To:	Kay Sievers <kay.sievers@...y.org>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Netdev List <netdev@...r.kernel.org>,
	Greg KH <greg@...ah.com>, David Miller <davem@...emloft.net>,
	Linux Containers <containers@...ts.osdl.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Benjamin Thery <benjamin.thery@...l.net>
Subject: Re: [patch 1/1][RFC]Handle uevent per namespace

Kay Sievers wrote:
> On Mon, Nov 24, 2008 at 11:50, Daniel Lezcano <dlezcano@...ibm.com> wrote:
> 
>  struct kobject {
>  	const char		*name;
>  	struct list_head	entry;
> @@ -63,6 +65,9 @@ struct kobject {
>  	struct kset		*kset;
>  	struct kobj_type	*ktype;
>  	struct sysfs_dirent	*sd;
> +#ifdef CONFIG_NET
> +	struct net              *net;
> +#endif
>  	struct kref		kref;
>  	unsigned int state_initialized:1;
>  	unsigned int state_in_sysfs:1;
> 
> We cannot do that. Network specific stuff does not belong into
> kobjects. Kobjects are not in any way subsystem specific, and we need
> to keep it that way.

That makes sense :)

Is there a way to follow up from the kobject, the netdev associated with 
it ? I mean in the function kobject_uevent_env, how can I check the 
event is related to a network device and retrieve the struct net_device 
from it ?

Thanks.
  -- Daniel

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html