All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: dilip.daya@hp.com
Cc: Chris J Arges <chris.j.arges@canonical.com>,
	Brian Haley <brian.haley@hp.com>,
	shemminger@osdl.org,
	"netdev\@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: iproute2: potential upgrade regression with 58a3e827
Date: Mon, 11 Nov 2013 14:40:47 -0800	[thread overview]
Message-ID: <871u2mblzk.fsf@xmission.com> (raw)
In-Reply-To: <1384205890.2758.28.camel@dilip-laptop> (Dilip Daya's message of "Mon, 11 Nov 2013 16:38:10 -0500")

Dilip Daya <dilip.daya@hp.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

  reply	other threads:[~2013-11-11 22:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 18:03 iproute2: potential upgrade regression with 58a3e827 Chris J Arges
2013-11-08 21:36 ` Eric W. Biederman
2013-11-08 22:30   ` Chris J Arges
2013-11-08 22:42     ` Eric W. Biederman
2013-11-09 17:00 ` Brian Haley
2013-11-11 21:26   ` Chris J Arges
2013-11-11 21:38     ` Dilip Daya
2013-11-11 22:40       ` Eric W. Biederman [this message]
2013-11-12  0:36         ` Dilip Daya
2013-12-13 18:46           ` [PATCH] " Chris J Arges
2013-12-13 18:55             ` Stephen Hemminger

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=871u2mblzk.fsf@xmission.com \
    --to=ebiederm@xmission.com \
    --cc=brian.haley@hp.com \
    --cc=chris.j.arges@canonical.com \
    --cc=dilip.daya@hp.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.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.