[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080423143610.GA13718@sergelap.austin.ibm.com>
Date: Wed, 23 Apr 2008 09:36:10 -0500
From: "Serge E. Hallyn" <serue@...ibm.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: "Serge E. Hallyn" <serue@...ibm.com>,
"H. Peter Anvin" <hpa@...or.com>,
Containers <containers@...ts.osdl.org>, clg@...ibm.com,
linux-kernel@...r.kernel.org, Pavel Emelyanov <xemul@...nvz.org>
Subject: Re: [RFC][PATCH 0/7] Clone PTS namespace
Quoting Eric W. Biederman (ebiederm@...ssion.com):
> "Serge E. Hallyn" <serue@...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?
Opinions?
thanks,
-serge
PS: If you want me to post the patchset before handling userns I can do
that, otherwise I was just going to wait until I'm done with userns.
--
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/
Powered by blists - more mailing lists