All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ram Pai <linuxram@us.ibm.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Al Viro <viro@ftp.linux.org.uk>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/18] cleanups and bug fix in do_loopback()
Date: Tue, 08 Nov 2005 00:46:07 -0800	[thread overview]
Message-ID: <1131439567.5400.221.camel@localhost> (raw)
In-Reply-To: <E1EZNRz-0007EM-00@dorka.pomaz.szeredi.hu>

On Mon, 2005-11-07 at 22:59, Miklos Szeredi wrote:
> > - check_mnt() on the source of binding should've been unconditional from
> > the very beginning.  My fault - as far I could've trace it, that's an
> > old thinko made back in 2001.  Kudos to Miklos for spotting it...
> > Fixed.
> > - code cleaned up.
> 
> Can you please explain what purpose does this serve?
> 
> AFAICS check_mnt() was there to ensure that operations are done under
> the proper namespace semaphore.

> Next in the series the namespace semaphore is made global, which
> basically means, that most of the check_mnt() invocations become
> useless.
> The ones which as a side effect prevent grafting to a detached mount
> can be changed to check for (mnt->mnt_namespace == NULL) instead of
> check against current->namespace.
> 
> I see no other reason for wanting to prevent binds from detached
> mounts or other namespaces.  It has been discussed that it would be a
> good _controlled_ way to send/receive mounts from other namespace
> without adding any complexity.

AFAICT, the ability to bind across namespaces defeats the private-ness
property of per-process-namespaces. 

RP



  reply	other threads:[~2005-11-08  8:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08  2:01 [PATCH 2/18] cleanups and bug fix in do_loopback() Al Viro
2005-11-08  6:59 ` Miklos Szeredi
2005-11-08  8:46   ` Ram Pai [this message]
2005-11-08  9:28     ` Miklos Szeredi
2005-11-09 19:08       ` Ram Pai
2005-11-09 21:15         ` Miklos Szeredi
2005-11-10  0:51           ` Ram Pai

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=1131439567.5400.221.camel@localhost \
    --to=linuxram@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@osdl.org \
    --cc=viro@ftp.linux.org.uk \
    /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.