[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 11 Nov 2013 14:40:47 -0800
From: ebiederm@...ssion.com (Eric W. Biederman)
To: dilip.daya@...com
Cc: Chris J Arges <chris.j.arges@...onical.com>,
Brian Haley <brian.haley@...com>, shemminger@...l.org,
"netdev\@vger.kernel.org" <netdev@...r.kernel.org>
Subject: Re: iproute2: potential upgrade regression with 58a3e827
Dilip Daya <dilip.daya@...com> writes:
> Hi Chris,
>
> On Mon, 2013-11-11 at 15:26 -0600, Chris J Arges wrote:
>
>> Good suggestion,
>> So I'll use a more simple example now:
>>
>> 1)
>> ip netns add first
>> ip netns exec first bash
>>
>> 2)
>> ip netns add second
>> ip netns exec second bash
>>
>> 3)
>> ip netns exec first bash
>>
>> If we do not upgrade the package, after we execute (2) we have:
>> # ls -l /var/run/netns
>> total 0
>> -r-------- 1 root root 0 Nov 11 20:38 first
>> -r-------- 1 root root 0 Nov 11 20:38 second
>>
>> If we upgrade after (1), then run (2) we have:
>> # ls -l /var/run/netns
>> total 0
>> ---------- 1 root root 0 Nov 11 20:56 first
>> -r-------- 1 root root 0 Nov 11 20:57 second
>>
>> So looks like netns add is doing something different from 58a3e827 and on.
I will just add that it is worth looking at /proc/mounts as well.
Although I have to admit that the difference in permissions is odd.
Eric
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists