Re: NFSd in container - it works

[Stanislav Kinsbursky <skinsbursky@parallels.com>]

29.11.2012 00:28, Jeff Layton пишет:
> On Wed, 28 Nov 2012 15:01:26 -0500
> "bfields@fieldses.org" <bfields@fieldses.org> wrote:
>
>>> 3) Holding net by tracker looks redundant. What was the reason for this?
>>
>> I don't understand, what's tracker?
>
> I assume he means the clientid tracker. That was necessary for the
> nfsdcld upcall because it used rpc_pipefs files, and those were
> net-namespacified. Once we deprecate that in 3.10, I don't think we'll
> need to worry about the net namespace in the clientid tracker.
>

Sorry, I don't understand. Rpc_pipefs superblock already holds network namespace.

> We probably *will* need to concern ourselves with the mnt namespace
> there though since each container will presumably have its own clientid
> database...

Since NFSd server in network namespace based, it means, that we can create one server for more than one mount namespace.
And clietid tracker holds files opened. Thus holds mount.
Mount namespace itself doesn't look that important to me.
Or I'm wrong?

-- 
Best regards,
Stanislav Kinsbursky