linux-kernel - Re: [PATCH 4/5] driver core: set up ownership of class devices in sysfs

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: <20160819192652.369f123e@xeon-e3>
Date:   Fri, 19 Aug 2016 19:26:52 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:     Tejun Heo <tj@...nel.org>,
        "Eric W. Biederman" <ebiederm@...ssion.com>,
        "David S. Miller" <davem@...emloft.net>,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH 4/5] driver core: set up ownership of class devices in
 sysfs

On Tue, 16 Aug 2016 15:33:14 -0700
Dmitry Torokhov <dmitry.torokhov@...il.com> wrote:

>  static struct kobj_type device_ktype = {
>  	.release	= device_release,
>  	.sysfs_ops	= &dev_sysfs_ops,
>  	.namespace	= device_namespace,
> +	.get_ownership	= device_get_ownership,
>  };
>  

OT - I wonder if kobj_type could be ro_after_init?