All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@parallels.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Stanislav Kinsbursky <skinsbursky@parallels.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"Kirill A. Shutemov" <kas@openvz.org>,
	"jlayton@redhat.com" <jlayton@redhat.com>
Subject: Re: network-namespace-aware nfsd
Date: Thu, 06 Oct 2011 17:14:17 +0400	[thread overview]
Message-ID: <4E8DA9A9.5010205@parallels.com> (raw)
In-Reply-To: <20111006131109.GB21627@fieldses.org>

On 10/06/2011 05:11 PM, J. Bruce Fields wrote:
> On Thu, Oct 06, 2011 at 04:29:51PM +0400, Pavel Emelyanov wrote:
>>>> Also, do you think per-namespace version support is important?
>>>>
>>>
>>> Actually, yes, I do.
>>> As I see it, nfsd filesystem have to virtualized to provide flexible control for 
>>> server features. If so, then we need to virtualize program as well.
>>
>> ACK - per namespace version control is required as well.
>>
>> AFAIK it's performed via sysctl-s and this part (sysctls engine I mean) is already
>> namespaces aware, thus it will not be the hard part of the implementation :)
> 
> It's a special file in the nfsd filesystem.  But I assume that won't be
> a big deal either.

Well, yes, you're right :)

> By the way, I'm curious: as we do this virtualization step-by-step, is
> there any way for userspace to tell how far we've gotten?
> 
> So for example if you have a system that's configured to use some new
> namespace-based feature, and you boot it to an old kernel, is there some
> way for it to check at the start and say "sorry, this isn't going to
> work"?

M-m... I'd say - there's no automatic way for doing this. What we can (and probably
should) do is - audit the nfs/nfsd subsystems and mark places with
   if (ns != &init_net_ns)
          return -EOPNOTSUPP
and remove these parts eventually.

> --b.
> .
> 


  reply	other threads:[~2011-10-06 13:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05 15:02 network-namespace-aware nfsd J. Bruce Fields
2011-10-05 17:26 ` Stanislav Kinsbursky
2011-10-05 18:19   ` J. Bruce Fields
2011-10-06  9:59     ` Stanislav Kinsbursky
2011-10-06 12:29       ` Pavel Emelyanov
2011-10-06 13:11         ` J. Bruce Fields
2011-10-06 13:14           ` Pavel Emelyanov [this message]
2011-10-06 13:18             ` Stanislav Kinsbursky
2011-10-06 16:46       ` J. Bruce Fields
2011-10-07 10:18         ` 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=4E8DA9A9.5010205@parallels.com \
    --to=xemul@parallels.com \
    --cc=bfields@fieldses.org \
    --cc=jlayton@redhat.com \
    --cc=kas@openvz.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 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.