From: Rob Landley <rlandley@parallels.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: <linux-kernel@vger.kernel.org>, <linux-nfs@vger.kernel.org>,
<containers@lists.linux-foundation.org>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
Tim Spriggs <tims@uahirise.org>,
Kir Kolyshkin <kir@parallels.com>,
Pavel Emelyanov <xemul@parallels.com>
Subject: Re: [PATCH 2/3] Supply network namespace to rpcbind.
Date: Wed, 6 Apr 2011 06:48:25 -0500 [thread overview]
Message-ID: <4D9C5309.1010700@parallels.com> (raw)
In-Reply-To: <20110406005743.GB27844@shutemov.name>
On 04/05/2011 07:57 PM, Kirill A. Shutemov wrote:
> On Thu, Mar 31, 2011 at 02:47:43AM -0500, Rob Landley wrote:
>> From: Rob Landley <rlandley@parallels.com>
>>
>> The sunrpc code already has some support for network namespaces,
>> but rpcb_create() is still using init_net. Its arguments include
>> a sockaddr and a port, but not a struct net *. Add one, and
>> pass in the value from rpc_xprt when calling it.
>>
>> Signed-off-by: Rob Landley <rlandley@parallels.com>
>
> Acked-by: Kirill A. Shutemov <kas@openvz.org>
>
> BTW, it seems conflicts with my rpc_pipefs patchset. I'll rebase my
> patchset, if your patches will be merged first.
And vice versa, lemme know which order you want them in.
Thanks,
Rob
next prev parent reply other threads:[~2011-04-06 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 7:47 [PATCH 2/3] Supply network namespace to rpcbind Rob Landley
2011-04-05 3:01 ` Serge E. Hallyn
2011-04-06 0:57 ` Kirill A. Shutemov
[not found] ` <20110406005743.GB27844-oKw7cIdHH8eLwutG50LtGA@public.gmane.org>
2011-04-06 11:48 ` Rob Landley
2011-04-06 11:48 ` Rob Landley [this message]
[not found] ` <4D94319F.8040005-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2011-04-05 3:01 ` Serge E. Hallyn
2011-04-06 0:57 ` Kirill A. Shutemov
-- strict thread matches above, loose matches on Subject: below --
2011-03-31 7:47 Rob Landley
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=4D9C5309.1010700@parallels.com \
--to=rlandley@parallels.com \
--cc=Trond.Myklebust@netapp.com \
--cc=containers@lists.linux-foundation.org \
--cc=kir@parallels.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tims@uahirise.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 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.