"Serge E. Hallyn" <serue@us.ibm.com> writes:

> Quoting Serge E. Hallyn (serue@us.ibm.com):
>> Quoting Eric W. Biederman (ebiederm@xmission.com):
>> > "Serge E. Hallyn" <serue@us.ibm.com> writes:
>> > >> 
>> > >> I'm hoping to be able to get back at this in the week or so as things
>> > >> settle down from my move.  My last patches should be in my proof of
>> > >> concept network namespace tree, if they don't show up elsewhere.
>> > >
>> > > Is that the tree I'd get from
>> > >
>> > > git-fetch
>> > > git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/linux-2.6-netns.git
>> > > master:ebieder.master
>> > 
>> > Yes.
>> > 
>> > > ?  So I'd add a user_ns to the struct sysfs_tag_info?
>> > >
>> > > If so I'll give it a whirl.
>> > 
>> > Sounds good.  My apologies I keep being almost on the verge
>> > of getting someplace.
>> 
>> Ok I've got the sysfs relevant patches ported to 2.6.25, and am looking
>> at how to extend it to handle /sys/kernel/uids.  You have tagging tied
>> intimately to struct class.  So the question is should I generalize the
>> taggint to deal with kobjects instead, or create a struct class user
>> and make /sys/kernel/uids a symlink to /sys/class/user/uids?
>
> Heh, never mind, I was thinking class was a kobject class, not a device
> class  :)  So I'll just have to generalize tagging.

Yes.  You just need a way to get the tags there.

At the level of sysfs it is fairly general.
Getting through the kobject layer is a different story.

I suspect since you are working on this and I seem to be stuck
in molasses at the moment it makes sense to figure out what it
will take to handle the uid namespace before pushing these
patches again.

Taking a quick look and having a clue what we will need to
do for a theoretical device namespace is also a possibility.

Eric
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers