linux-kernel - Re: [PATCH 2/2] Implement shadow directory support for device classes.

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: <m1y7nsyxsp.fsf@ebiederm.dsl.xmission.com>
Date:	Wed, 24 Jan 2007 13:28:22 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Greg KH <gregkh@...e.de>
Cc:	linux-kernel@...r.kernel.org,
	Linux Containers <containers@...ts.osdl.org>,
	linux-fsdevel@...r.kernel.org, Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH 2/2] Implement shadow directory support for device classes.

Greg KH <gregkh@...e.de> writes:

> On Wed, Jan 24, 2007 at 12:37:19PM -0700, Eric W. Biederman wrote:
>> 
>> Modify the device class code so that normal manipulations work
>> in the presence of shadow directories.  Some of the shadow directory
>> support still needs to be implemented in the implementation of the
>> class but these modifications are sufficient to make that simple.
>
> This is a nice idea, but I'm working to get rid of 'struct class_device'
> from the tree.  Network devices have already been converted, the patch
> is in the -mm tree, I'm working on some firewire fixes before pushing it
> to Linus.
>
> So, I think you want to do this work for 'struct device' too, as that is
> what will be the real user of this code.

Sure.  That shouldn't be too hard.

Is any of that work in Dave Millers' networking tree?

I'm just trying to figure out where your work is, relative to the rest of
the networking stack.

I have a lot of networking infrastructure I need to touch.

Eric
-
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/