From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: linux-nfs@vger.kernel.org, Trond.Myklebust@netapp.com,
linux-kernel@vger.kernel.org, devel@openvz.org
Subject: Re: [PATCH v2 0/4] nfsd: make is works in a container
Date: Fri, 15 Feb 2013 11:20:21 -0500 [thread overview]
Message-ID: <20130215162021.GK8343@fieldses.org> (raw)
In-Reply-To: <20130201125210.3257.46454.stgit@localhost.localdomain>
On Fri, Feb 01, 2013 at 03:56:05PM +0300, Stanislav Kinsbursky wrote:
> This patch set finally enables NFSd in container.
> I've tested it in container with it's own root, and also pid, net and mount
> namespaces.
Thanks, these look fine to me; applying. They should show up in my
for-3.9 branch sometime today.
--b.
>
> There are some limitations, which are listed below:
> 1) only nfsdclt client tracker supported for container. It's deprecated and
> going to be removed soon. UMH tracker requires switching root. Legacy tracker
> requires something like RB tree of opened inodes to make sure, that any
> recovery directory will be opened only once.
> 2) Enabled versions are controlled globally (should be fixed).
> 3) Server should be stopped by writing "0" to
> /proc/fs/nfsd/threads instead of sending signals to NFSd threads (they are
> working in init_pid). Sending signals will either won't work if container wich
> its own pid namespace, or will kill all nfsd threads for all containers in
> init_pid namesapce.
> 4) Currently, if container was stopped without stopping NFS server (i.e. it's
> init was killed), NFSd kthreads will remain running. One of possible solutions
> is to not hold network by NFSd service sockets, but register oer-net callback
> and kill all the threads on network namespace exit.
> 5) NFSd filesystem superblock holds network namespace. I.e. if some process
> will hold container's NFSd supeblock, then sthe whole container's network
> naemspace will stay alive even is container is destroyed already.
>
> There may be more limitations, which are not clear to me yet.
>
> v2:
> 1) removed root swap - deprecated
> 2) rebased on current tree
>
> The following series implements...
>
> ---
>
> Stanislav Kinsbursky (4):
> nfsd: containerize NFSd filesystem
> nfsd: use proper net while reading "exports" file
> nfsd: disable usermode helper client tracker in container
> nfsd: enable NFSv4 state in containers
>
>
> fs/nfsd/nfs4recover.c | 6 ++++
> fs/nfsd/nfs4state.c | 10 ------
> fs/nfsd/nfsctl.c | 77 +++++++++++++++++++++++++++++++++++++------------
> fs/nfsd/nfssvc.c | 5 +--
> 4 files changed, 66 insertions(+), 32 deletions(-)
>
next prev parent reply other threads:[~2013-02-15 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 12:56 [PATCH v2 0/4] nfsd: make is works in a container Stanislav Kinsbursky
2013-02-01 12:56 ` [PATCH 1/4] nfsd: containerize NFSd filesystem Stanislav Kinsbursky
2013-02-01 12:56 ` [PATCH 2/4] nfsd: use proper net while reading "exports" file Stanislav Kinsbursky
2013-02-01 12:56 ` [PATCH 3/4] nfsd: disable usermode helper client tracker in container Stanislav Kinsbursky
2013-02-01 12:56 ` [PATCH 4/4] nfsd: enable NFSv4 state in containers Stanislav Kinsbursky
2013-02-15 16:20 ` J. Bruce Fields [this message]
2013-02-18 5:10 ` [PATCH v2 0/4] nfsd: make is works in a container 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=20130215162021.GK8343@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=devel@openvz.org \
--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