All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Jeff Layton <jlayton@redhat.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH][RFC] nfsd/lockd: have locks_in_grace take a sb arg
Date: Thu, 12 Apr 2012 13:05:59 +0400	[thread overview]
Message-ID: <4F869AF7.10901@parallels.com> (raw)
In-Reply-To: <20120411221729.GG31706@fieldses.org>

12.04.2012 02:17, J. Bruce Fields пишет:
> On Wed, Apr 11, 2012 at 11:24:52PM +0400, Stanislav Kinsbursky wrote:
>> 11.04.2012 22:22, J. Bruce Fields написал:
>>>>>   What would happen, if we will have situation like below:
>>>>>   >   	mountd A	mountd B
>>>>>   >   	pid_ns		pid_ns
>>>>>   	|		  |
>>>>>   	mnt_ns		mnt_ns
>>>>>   	|		  |
>>>>>   	-----	net_ns ----
>>>>>   >   Is it possible, BTW?
>>>>>   It yes, that is such construction valid?
>>> Looks like a mess, no.  I'd expect there to be only one rpc.mountd
>>> running per network namespace.
>>
>> Then we have to prevent such situations somehow.
>> Or it is done already?
>
> If there's a way to prevent it, great, otherwise I think we just tell
> people not to do that, and make sure any distro scripts (or whatever)
> don't do that.
>

Sure, there is a way.
For example, mountd will need to ask kernel is he allowed to start or not. 
Kernel will have to compare starting mountd mount namespace with the mount 
namespace of the previous started mountd process. If they matches or previous 
mountd process is dead (or even never started), then new start is allowed.
And disallowed otherwise.

> Actually, my statement above isn't quite right: we do allow running
> multiple rpc.mountd processes in one network namespace (see the
> --num-threads option to rpc.mountd, which is sometimes necessary for
> performance).  But they should all be in the same namespaces and be
> using the same configuration.
>
> --b.


-- 
Best regards,
Stanislav Kinsbursky

  reply	other threads:[~2012-04-12  9:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03 12:14 [PATCH][RFC] nfsd/lockd: have locks_in_grace take a sb arg Jeff Layton
2012-04-09 23:18 ` J. Bruce Fields
2012-04-10 11:13   ` Jeff Layton
2012-04-10 13:18     ` J. Bruce Fields
2012-04-10 11:44 ` Stanislav Kinsbursky
2012-04-10 12:05   ` Jeff Layton
2012-04-10 12:18     ` Stanislav Kinsbursky
2012-04-10 12:16   ` Jeff Layton
2012-04-10 12:46     ` Stanislav Kinsbursky
2012-04-10 13:39       ` Jeff Layton
2012-04-10 14:52         ` Stanislav Kinsbursky
2012-04-10 18:45           ` Jeff Layton
2012-04-11 10:09             ` Stanislav Kinsbursky
2012-04-11 11:48               ` Jeff Layton
2012-04-11 13:08                 ` Stanislav Kinsbursky
2012-04-11 17:19                   ` J. Bruce Fields
2012-04-11 17:37                     ` Stanislav Kinsbursky
2012-04-11 18:22                       ` J. Bruce Fields
2012-04-11 19:24                         ` Stanislav Kinsbursky
2012-04-11 22:17                           ` J. Bruce Fields
2012-04-12  9:05                             ` Stanislav Kinsbursky [this message]
2012-04-10 20:22       ` J. Bruce Fields
2012-04-11 10:34         ` Stanislav Kinsbursky
2012-04-11 17:20           ` J. Bruce Fields
2012-04-11 17:33             ` Stanislav Kinsbursky
2012-04-11 17:40               ` Stanislav Kinsbursky
2012-04-11 18:20               ` J. Bruce Fields
2012-04-11 19:39                 ` Stanislav Kinsbursky
2012-04-11 19:54                   ` 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=4F869AF7.10901@parallels.com \
    --to=skinsbursky@parallels.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 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.