mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: Dilip Daya <dilip.daya@hp.com>
Cc: linux-kernel@vger.kernel.org,
	containers@lists.linux-foundation.org,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: Network namespace and bonding WARNING at fs/proc/generic.c remove_proc_entry
Date: Thu, 5 Jul 2012 22:07:49 +0000	[thread overview]
Message-ID: <20120705220749.GA11255@mail.hallyn.com> (raw)
In-Reply-To: <1340900320.3441.88.camel@pro6455b.example.com>

Quoting Dilip Daya (dilip.daya@hp.com):
> Hi,
> 
> I'd discussed the following with Serge Hallyn.
> 
> => Environment based on 3.2.18 / x86_64 kernel.
> => WARNING: at fs/proc/generic.c:808 remove_proc_entry+0xdb/0x21f()
> => WARNING: at fs/proc/generic.c:849 remove_proc_entry+0x208/0x21f()

Hi,

thanks much for sending this.  I'm still getting this error on
3.5.0-2-generic (today's ubuntu quantal kernel)

> network namespace and bonding
> -----------------------------
> 
> * Migrate two phy nics from host to netns (netns0).
>   - ip link set ethX netns netns0
> 
> * In host environment:
>   - load bonding module, /sbin/modprobe -v bonding mode=1 miimon=100
>   - /sys/class/net/bond0 exists.
>   - /proc/net/bonding/bond0 exists.
>   - /sys/class/net/bonding_masters has bond0.
> 
> * Migrate bond0 to netns (netns0):
>   - ip link set bond0 netns netns0.
> 
> * Within netns (netns0):
>   - /sys/class/net/bonding_masters is empty.
>   - /sys/class/net/bond0 exist.
>   - configure bond0 and ifenslave with two phy nics.
>   - /proc/net/bonding/bond0 does not exist within netns0, but does
>     exist in the host environment.
>   - /sys/class/net/bonding_masters is empty.

mine is not empty, fwiw.  However

>   - ping to remote end of bond0 works.
> 
> * Within netns (netns0), flushing ethX and bondY:
>   - down bond0 and its phy nic interfaces:
>   - ip link set ... down
>   - ip addr flush dev [bond0 | eth#]
>   - deleting bond0, /sbin/ip link del dev bond0

Yup I still get a remove_proc_entry WARNING at fs/proc/generic.c:808,
which is the warning when (!de)

-serge

  reply	other threads:[~2012-07-05 22:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 16:18 Dilip Daya
2012-07-05 22:07 ` Serge E. Hallyn [this message]
2012-07-06  0:41   ` Eric W. Biederman
2012-07-06 17:05     ` Serge E. Hallyn
2012-07-06 18:01       ` Dilip Daya
2012-07-06 18:57       ` Eric W. Biederman
2012-07-06 19:47         ` Serge E. Hallyn
2012-07-09 20:51           ` [PATCH 1/2] bonding: Manage /proc/net/bonding/ entries from the netdev events Eric W. Biederman
2012-07-09 20:52             ` [PATCH 2/2] bonding: debugfs and network namespaces are incompatible Eric W. Biederman
2012-07-09 21:49               ` David Miller
2012-07-10 17:36                 ` Jay Vosburgh
2012-07-09 21:49             ` [PATCH 1/2] bonding: Manage /proc/net/bonding/ entries from the netdev events David Miller
2012-07-06 18:01     ` Network namespace and bonding WARNING at fs/proc/generic.c remove_proc_entry Dilip Daya
2012-07-06 18:40       ` Eric W. Biederman

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=20120705220749.GA11255@mail.hallyn.com \
    --to=serge@hallyn.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=dilip.daya@hp.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome