From: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
To: Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>,
"Denis V. Lunev" <den-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Cc: Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
Benjamin Thery <benjamin.thery-6ktuUTfB/bM@public.gmane.org>,
Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>,
"Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Subject: Re: Pid namespaces problems
Date: Thu, 08 Nov 2007 13:40:37 +0300 [thread overview]
Message-ID: <4732E7A5.6050703@openvz.org> (raw)
In-Reply-To: <4731F4BC.4000203-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
Daniel Lezcano wrote:
> Pavel Emelyanov wrote:
>> Daniel Lezcano wrote:
>>> Cedric Le Goater wrote:
>>>>>> - There are several architectures with their own signal functions for
>>>>>> other OS compatibility that have are using _pid and not _vpid
>>>>>> variants of functions. (irix and solaris)
>>>>>> arch/mips/kernel/irixsig.c:irix_waitsys
>>>>>> arch/mips/kernel/sysirix.c:irix_setpgrp
>>>>>> arch/sparc64/solaris/misc.c:solaris_procids
>>>>> Ok. Looks like your list is the same as mine. That's good to hear
>>>>> that I haven't missed anything important.
>>>> We've also talked about af_unix credentials.
>>>>
>>>>> So, I see that you're about to take a closer look at the pid
>>>>> namespaces. If so, then what time can we expect the net namespace
>>>>> activity to go on? Or (if you don't mind) can we start merging
>>>>> the patches to David as soon as he opens his 2.6.25 merge window?
>>>> I think daniel and benjamin are also getting ready for the 2.6.25
>>>> merge window.
>>> Yes. It can be cool if we can sync up Benjamin, Pavel, Denis, Eric and I
>>> with the different parts to be posted.
>> Yup. Team work will give us a chance to get in to the 2.6.25 with
>> the core virtualization. By core I mean unix, netlinux, ipv4 and ipv6.
>
> Yeah, if we can push these protocols in time, that will be *very very*
> cool :)
>
> When you talk about ipv4/ipv6 do you include tcp/udp ?
>
>> Netfilters virtualization is a complex task :)
>>
>>> Benjamin and I we began to look
>>> at ipv4. This is a big part, perhaps we can split that into several
>>> subset and dispatch them, except if Pavel and Denis already rebase ipv4
>>> for net-2.6, in this case feel free to send them out.
>> Well, actually we have almost moved to the net-2.6 with the ipv4
>> set.
>
> Excellent !
> Did you took the different patches I sent for udplite and multicast ?
Not yet, sorry. But we will look at them as soon as we finish with
the existing netns tree.
> If you rebased netns49 to net-2.6 and you plan to keep synced with the
> Dave Miller tree, perhaps it is time to switch the git tree.
> It can be cool if you can put a git tree at openvz.
Sure, but right now we don't have a git repo with it :( We
just have a series of patches, some of them are fixes, some
not. We are going to re-split them and publish to git. I think
that the next week the git.openvz.org will have that repo.
What about your ipv6? Do you have a git repo with it?
>> There are only some minor (I hope they are minor ;)) things.
>
> Perhaps, we can help here.
Yes, of course. When we publish the git repo we'll try to
provide a TODO list so that everyone can participate.
>> So we would be glad to go on with ipv4 further. What's up with the
>> ipv6 patches, Daniel? You said that you and Benjamin make some
>> big progress in this area, no?
>
> Yes, for the moment we reach the addrconf stuff, so we have routing
> table, ip6_fib, fib6_rules, ndisc and addrconf per namespaces.
> The patches sent by Alexey Dobriyan making /proc/net/ipv6_route to the
> seq_file interface has made our life easier.
:) We plan to make some cleanups in the networking code that
make sense even now, but are useful for namespaces.
> IMHO this part of ipv6 is the most difficult, the different protocols
> relying on it will be much more easy to implement.
>
> We are actually facing two problems:
>
> * the first one is the locking of the network namespace list by
> rtnl_lock, so from the timer callback we can not browse the network
> namespace list to check the age of the routes. It is a problem I would
> like to talk with Denis if he has time
Sure. I will kick him in case he missed it accidentally :)
> * the loopback refcounting is not correctly handled in ipv6. This
> protocol do not expect to have the loopback to be unregistered, so there
> is some problem with the addr_ifdown function when exiting the network
> namespace
Hm! This is one of the issues we can send to David right now. Do
you have any patches? If not, I can take care of it if you don't mind.
> Regards.
> -- Daniel
>
Thanks,
Pavel
next prev parent reply other threads:[~2007-11-08 10:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <472AE42F.5000602@openvz.org>
[not found] ` <472AE42F.5000602-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-04 4:06 ` Pid namespaces problems Eric W. Biederman
[not found] ` <m1640id57r.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
2007-11-06 7:39 ` Pavel Emelyanov
[not found] ` <47301A14.9040304-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-06 16:28 ` Eric W. Biederman
2007-11-07 8:28 ` Cedric Le Goater
[not found] ` <4731772D.3060806-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-07 8:18 ` Daniel Lezcano
2007-11-07 9:00 ` Daniel Lezcano
[not found] ` <47317EA7.6030500-GANU6spQydw@public.gmane.org>
2007-11-07 16:12 ` Pavel Emelyanov
[not found] ` <4731E3DE.6000501-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-07 17:24 ` Daniel Lezcano
[not found] ` <4731F4BC.4000203-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-08 10:40 ` Pavel Emelyanov [this message]
[not found] ` <4732E7A5.6050703-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-08 11:07 ` Daniel Lezcano
2007-11-08 10:53 ` Denis V. Lunev
[not found] ` <4732EA8E.7080400-3ImXcnM4P+0@public.gmane.org>
2007-11-08 13:29 ` Daniel Lezcano
[not found] ` <47330F1F.4080806-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-08 13:37 ` Pavel Emelyanov
[not found] ` <47331122.3000304-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-08 13:42 ` net namespace plans for 2.6.25 (was Re: Pid namespaces problems) Cedric Le Goater
[not found] ` <47331241.2090501-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-08 13:45 ` Daniel Lezcano
[not found] ` <473312FD.5030609-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-08 13:58 ` Pavel Emelyanov
[not found] ` <473315F5.20608-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-08 14:08 ` Benjamin Thery
2007-11-08 14:09 ` Daniel Lezcano
[not found] ` <473318A0.7010509-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-09 10:14 ` Pavel Emelyanov
2007-11-08 14:05 ` Denis V. Lunev
[not found] ` <473317A2.2020307-3ImXcnM4P+0@public.gmane.org>
2007-11-08 14:00 ` Daniel Lezcano
2007-11-08 13:43 ` Pid namespaces problems Denis V. Lunev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4732E7A5.6050703@openvz.org \
--to=xemul-gefaqzzx7r8dnm+yrofe0a@public.gmane.org \
--cc=benjamin.thery-6ktuUTfB/bM@public.gmane.org \
--cc=clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=den-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.