From: Weng Meiling <wengmeiling.weng@huawei.com>
To: "J. Bruce Fields" <bfields@fieldses.org>,
Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: <greg@kroah.com>, <linux-nfs@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devel@openvz.org>
Subject: Re: [PATCH] nfsd: check passed socket's net matches NFSd superblock's one
Date: Tue, 18 Feb 2014 21:06:47 +0800 [thread overview]
Message-ID: <53035AE7.5030208@huawei.com> (raw)
In-Reply-To: <20140217221900.GA8401@fieldses.org>
Hi Bruce , Stanislav
On 2014/2/18 6:19, J. Bruce Fields wrote:
> On Sat, Feb 15, 2014 at 09:51:20AM +0800, Weng Meiling wrote:
>> Hi Bruce,
>>
>> The upstream has merged your git tree for-3.14, but there is no this patch?
>> Do you forget this patch?
>
> Apologies, I'm not sure what happened.
>
> Looking back at it.... The patch causes all my pynfs reboot recovery
> tests to fail. They're just doing a "systemctl restart
> nfs-server.service", and "systemctl status nfs-server.service" shows in
> part
>
> ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS $RPCNFSDCOUNT (code=exited, status=1/FAILURE)
>
> So the patch is causing rpc.nfsd to fail? No network namespaces should
> be involved.
>
> I haven't investigated any further.
>
the problem exists. Sorry for careless testing.
Stanislav, how do you think about this?
Thanks!
Weng Meiling
> --b.
>
>>
>> Thanks!
>> Weng Meiling
>>
>>
>> On 2014/1/4 6:22, J. Bruce Fields wrote:
>>> On Mon, Dec 30, 2013 at 05:23:59PM +0300, Stanislav Kinsbursky wrote:
>>>> There could be a case, when NFSd file system is mounted in network, different
>>>> to socket's one, like below:
>>>>
>>>> "ip netns exec" creates new network and mount namespace, which duplicates NFSd
>>>> mount point, created in init_net context. And thus NFS server stop in nested
>>>> network context leads to RPCBIND client destruction in init_net.
>>>> Then, on NFSd start in nested network context, rpc.nfsd process creates socket
>>>> in nested net and passes it into "write_ports", which leads to RPCBIND sockets
>>>> creation in init_net context because of the same reason (NFSd monut point was
>>>> created in init_net context). An attempt to register passed socket in nested
>>>> net leads to panic, because no RPCBIND client present in nexted network
>>>> namespace.
>>>
>>> So it's the attempt to use a NULL ->rpcb_local_clnt4?
>>>
>>> Interesting, thanks--applying with a minor fix to logged message.
>>>
>>> --b.
>>>
>>
>>
>>
>
> .
>
next prev parent reply other threads:[~2014-02-18 13:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 14:23 [PATCH] nfsd: check passed socket's net matches NFSd superblock's one Stanislav Kinsbursky
2014-01-03 22:22 ` J. Bruce Fields
2014-01-09 7:15 ` Stanislav Kinsbursky
2014-02-15 1:51 ` Weng Meiling
2014-02-17 22:19 ` J. Bruce Fields
2014-02-18 13:06 ` Weng Meiling [this message]
2014-02-18 15:19 ` Stanislav Kinsbursky
2014-02-18 15:44 ` J. Bruce Fields
2014-02-19 10:26 ` Stanislav Kinsbursky
2014-02-19 14:50 ` J. Bruce Fields
2014-02-19 14:57 ` Stanislav Kinsbursky
2014-02-20 21:31 ` J. Bruce Fields
2014-02-21 9:18 ` Stanislav Kinsbursky
-- strict thread matches above, loose matches on Subject: below --
2014-02-26 13:50 Stanislav Kinsbursky
2014-03-31 20:58 ` J. Bruce Fields
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=53035AE7.5030208@huawei.com \
--to=wengmeiling.weng@huawei.com \
--cc=bfields@fieldses.org \
--cc=devel@openvz.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=skinsbursky@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).