linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "Trond.Myklebust@netapp.com" <Trond.Myklebust@netapp.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	Pavel Emelianov <xemul@parallels.com>,
	"neilb@suse.de" <neilb@suse.de>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	James Bottomley <jbottomley@parallels.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"devel@openvz.org" <devel@openvz.org>
Subject: Re: [PATCH 0/4] SUNRPC: pass network namespace context to sockaddr construction routines
Date: Mon, 12 Dec 2011 20:13:24 +0400	[thread overview]
Message-ID: <4EE62824.9090807@parallels.com> (raw)
In-Reply-To: <20111208204648.GB32505@fieldses.org>

09.12.2011 00:46, J. Bruce Fields пишет:
> On Wed, Dec 07, 2011 at 03:20:07PM +0300, Stanislav Kinsbursky wrote:
>> This is another precursor patch set aimed to remove hard-coded "init_net"
>> reference from SUNRPC sockaddr convertion and construction routines.
>
> ACK--all look straightforward.  (Only complaint would be that this isn't
> terribly interesting till we see how these are used.)
>

Actually, all is simple. These init_net pointers will be replaced later by 
"transports, clients and others" network namespace contexts.
I have some more patches for NFS layer. But I don't see any sense to sent them 
now since no "virtualization" patches were commited yet.
So, currently, I'm trying to finalize "SUNRPC per network namespace" task, and 
soon I'll send a patch set making SUNRPC sysctl's network-namespace-aware. It is 
a little bit tricky and ugly from my pow, so any ideas are welcome.

> --b.
>
>
>>
>> The following series consists of:
>>
>> ---
>>
>> Stanislav Kinsbursky (4):
>>        SUNRPC: use passed network namespace context in rpc_parse_scope_id()
>>        SUNRPC: use passed network namespace context in rpc_pton6()
>>        SUNRPC: use passed network namespace context in rpc_pton()
>>        SUNRPC: use passed network namespace context in rpc_uaddr2sockaddr()
>>
>>
>>   fs/nfs/dns_resolve.c        |    4 ++--
>>   fs/nfs/nfs4filelayoutdev.c  |    2 +-
>>   fs/nfs/nfs4namespace.c      |    2 +-
>>   fs/nfs/super.c              |    4 ++--
>>   fs/nfsd/nfs4state.c         |    2 +-
>>   fs/nfsd/nfsctl.c            |    2 +-
>>   include/linux/sunrpc/clnt.h |    4 ++--
>>   net/sunrpc/addr.c           |   24 +++++++++++++-----------
>>   net/sunrpc/rpcb_clnt.c      |    2 +-
>>   net/sunrpc/svcauth_unix.c   |    2 +-
>>   10 files changed, 25 insertions(+), 23 deletions(-)
>>
>> --
>> Signature


-- 
Best regards,
Stanislav Kinsbursky

  reply	other threads:[~2011-12-12 16:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 12:20 [PATCH 0/4] SUNRPC: pass network namespace context to sockaddr construction routines Stanislav Kinsbursky
2011-12-07 12:20 ` [PATCH 1/4] SUNRPC: use passed network namespace context in rpc_parse_scope_id() Stanislav Kinsbursky
2011-12-08 20:47   ` J. Bruce Fields
2011-12-12 16:03     ` Stanislav Kinsbursky
2011-12-12 16:07       ` J. Bruce Fields
2011-12-12 16:18         ` Stanislav Kinsbursky
2011-12-07 12:20 ` [PATCH 2/4] SUNRPC: use passed network namespace context in rpc_pton6() Stanislav Kinsbursky
2011-12-07 12:20 ` [PATCH 3/4] SUNRPC: use passed network namespace context in rpc_pton() Stanislav Kinsbursky
2011-12-07 12:20 ` [PATCH 4/4] SUNRPC: use passed network namespace context in rpc_uaddr2sockaddr() Stanislav Kinsbursky
2011-12-08 20:46 ` [PATCH 0/4] SUNRPC: pass network namespace context to sockaddr construction routines J. Bruce Fields
2011-12-12 16:13   ` Stanislav Kinsbursky [this message]
2011-12-12 16:15     ` J. Bruce Fields
2011-12-12 16:27       ` Stanislav Kinsbursky

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=4EE62824.9090807@parallels.com \
    --to=skinsbursky@parallels.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=davem@davemloft.net \
    --cc=devel@openvz.org \
    --cc=jbottomley@parallels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=netdev@vger.kernel.org \
    --cc=xemul@parallels.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;
as well as URLs for NNTP newsgroup(s).