From: David Miller <davem@davemloft.net>
To: ebiederm@xmission.com
Cc: dilip.daya@hp.com, linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org, netdev@vger.kernel.org,
serge@hallyn.com
Subject: Re: [PATCH 1/2] bonding: Manage /proc/net/bonding/ entries from the netdev events
Date: Mon, 09 Jul 2012 14:49:26 -0700 (PDT) [thread overview]
Message-ID: <20120709.144926.373399647799528683.davem@davemloft.net> (raw)
In-Reply-To: <87y5ms3bfi.fsf_-_@xmission.com>
From: ebiederm@xmission.com (Eric W. Biederman)
Date: Mon, 09 Jul 2012 13:51:45 -0700
>
> It was recently reported that moving a bonding device between network
> namespaces causes warnings from /proc. It turns out after the move we
> were trying to add and to remove the /proc/net/bonding entries from the
> wrong network namespace.
>
> Move the bonding /proc registration code into the NETDEV_REGISTER and
> NETDEV_UNREGISTER events where the proc registration and unregistration
> will always happen at the right time.
>
> Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Applied.
next prev parent reply other threads:[~2012-07-09 21:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 16:18 Network namespace and bonding WARNING at fs/proc/generic.c remove_proc_entry Dilip Daya
2012-07-05 22:07 ` Serge E. Hallyn
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 ` David Miller [this message]
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=20120709.144926.373399647799528683.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=containers@lists.linux-foundation.org \
--cc=dilip.daya@hp.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=serge@hallyn.com \
/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
all inboxes | Powered by JetHome®