From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: "bfields@fieldses.org" <bfields@fieldses.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
Jeff Layton <jlayton@redhat.com>,
"Trond.Myklebust@netapp.com" <Trond.Myklebust@netapp.com>
Subject: NFSd in container - it works
Date: Wed, 28 Nov 2012 21:13:12 +0400 [thread overview]
Message-ID: <50B64628.4070007@parallels.com> (raw)
Hi.
I have about ~10 more patches, which makes NFS server works in container (mnt + pid + net namesapces). And it passes basic tests.
But there are some issues I would like to discuss:
1) NFSd threads are running in init_pid namespace. This makes impossible to stop NFS server by signals from container. Also is makes possible to stop and
destroy container without stopping its NFS server (network namespace thus will stay alive). So, there should be implemented some way to destroy these threads,
when container's child reaper is exiting.
2) We need to solve this issue with registering in wrong portmapper. Sync connects suits both Lockd and NFSd. Bruce, what about gss daemon? Maybe some other
socket (abstract UNIX or loopback) can be used instead? Or PipeFS?
3) Holding net by tracker looks redundant. What was the reason for this?
--
Best regards,
Stanislav Kinsbursky
next reply other threads:[~2012-11-28 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 17:13 Stanislav Kinsbursky [this message]
2012-11-28 20:01 ` NFSd in container - it works bfields
2012-11-28 20:28 ` Jeff Layton
2012-11-29 11:53 ` Stanislav Kinsbursky
2012-11-29 12:13 ` Jeff Layton
2012-11-29 12:48 ` Stanislav Kinsbursky
2012-11-29 12:55 ` Jeff Layton
2012-11-29 13:04 ` Stanislav Kinsbursky
2012-11-29 14:11 ` Stanislav Kinsbursky
2012-11-29 11:34 ` 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=50B64628.4070007@parallels.com \
--to=skinsbursky@parallels.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/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).