All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao feng <gaofeng@cn.fujitsu.com>
To: Gao feng <gaofeng@cn.fujitsu.com>
Cc: davem@davemloft.net, eric.dumazet@gmail.com,
	steffen.klassert@secunet.com, netdev@vger.kernel.org,
	containers@lists.linux-foundation.org
Subject: Re: [PATCH net-next v3 1/2] inetpeer: add namespace support for inetpeer
Date: Fri, 08 Jun 2012 21:26:42 +0800	[thread overview]
Message-ID: <4FD1FD92.1050301@cn.fujitsu.com> (raw)
In-Reply-To: <1339154441-4513-1-git-send-email-gaofeng@cn.fujitsu.com>

于 2012年06月08日 19:20, Gao feng 写道:
> now inetpeer doesn't support namespace,the information will
> be leaking across namespace.
> 
> this patch move the global vars v4_peers and v6_peers to
> netns_ipv4 and netns_ipv6 as a field peers.
> 
> add struct pernet_operations inetpeer_ops to initial pernet
> inetpeer data.
> 
> and change family_to_base and inet_getpeer to support namespace.
> 
> Signed-off-by: Gao feng <gaofeng@cn.fujitsu.com>
> ---

It seams I send two v3 patch.
Please ignore this duplicate,There must be some wrong with my mail client.

Thanks Eric for reminding me this.

  parent reply	other threads:[~2012-06-08 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 11:20 [PATCH net-next v3 1/2] inetpeer: add namespace support for inetpeer Gao feng
     [not found] ` <1339154441-4513-1-git-send-email-gaofeng-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2012-06-08 11:21   ` [PATCH net-next v3 2/2] inetpeer: add parameter net for inet_getpeer_v4, v6 Gao feng
2012-06-08 13:26   ` [PATCH net-next v3 1/2] inetpeer: add namespace support for inetpeer Gao feng
2012-06-08 13:26 ` Gao feng [this message]
     [not found] <1339137683-19217-1-git-send-email-gaofeng@cn.fujitsu.com>
2012-06-08 21:27 ` David Miller
     [not found] ` <1339137683-19217-1-git-send-email-gaofeng-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2012-06-08 21:27   ` David Miller

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=4FD1FD92.1050301@cn.fujitsu.com \
    --to=gaofeng@cn.fujitsu.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=steffen.klassert@secunet.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 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.