linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ram Pai <linuxram@us.ibm.com>
To: Valerie Aurora <vaurora@redhat.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Erez Zadok <ezk@cs.sunysb.edu>
Subject: Re: [PATCH] VFS: Clean up shared mount flag propagation
Date: Fri, 29 Jan 2010 09:52:17 -0800	[thread overview]
Message-ID: <1264787537.6643.144.camel@localhost> (raw)
In-Reply-To: <20100126192047.GB32353@shell>

On Tue, 2010-01-26 at 14:20 -0500, Valerie Aurora wrote:
> Al, you might have already fixed this as part of your mount flag
> rewrite, but here's a patch to clean up some problems with shared
> mount flag propagation that I ran into while working on union mounts.
> Against 2.6.32.
> 
> -VAL
> 
> commit 3f436c4466f278900d451494b317f6bb80b4c24b
> Author: Valerie Aurora <vaurora@redhat.com>
> Date:   Tue Jan 26 11:09:00 2010 -0800
> 
>     VFS: Clean up shared mount flag propagation
>     
>     The handling of mount flags in set_mnt_shared() got a little tangled
>     up during previous cleanups, with the following problems:
>     
>     * MNT_PNODE_MASK is defined as a literal constant when it should be a
>       bitwise xor of other MNT_* flags
>     * set_mnt_shared() clears and then sets MNT_SHARED (part of MNT_PNODE_MASK)
>     * MNT_PNODE_MASK could use a comment in mount.h
>     * MNT_PNODE_MASK is a terrible name, change to MNT_SHARED_MASK
>     
>     This patch fixes these problems.
> 
> diff --git a/fs/pnode.h b/fs/pnode.h
> index 958665d..adc52ca 100644
> --- a/fs/pnode.h
> +++ b/fs/pnode.h
> @@ -26,7 +26,7 @@
> 
>  static inline void set_mnt_shared(struct vfsmount *mnt)
>  {
> -	mnt->mnt_flags &= ~MNT_PNODE_MASK;
> +	mnt->mnt_flags &= ~MNT_SHARED_MASK;
>  	mnt->mnt_flags |= MNT_SHARED;
>  }
> 

Is resetting the MNT_SHARED bit and setting it back, causing a issue?

If so, why not just do
  -      mnt->mnt_flags &=  ~MNT_PNODE_MASK;
  +      mnt->mnt_flags &=  ~MNT_UNBINDABLE; 





> diff --git a/include/linux/mount.h b/include/linux/mount.h
> index 5d52753..257985f 100644
> --- a/include/linux/mount.h
> +++ b/include/linux/mount.h
> @@ -34,7 +34,15 @@ struct mnt_namespace;
> 
>  #define MNT_SHARED	0x1000	/* if the vfsmount is a shared mount */
>  #define MNT_UNBINDABLE	0x2000	/* if the vfsmount is a unbindable mount */
> -#define MNT_PNODE_MASK	0x3000	/* propagation flag mask */

I prefer to leave the name MNT_PNODE_MASK as is, because it captures the
notion of propagation v/s the notion of just being shared.

> +/*
> + * MNT_SHARED_MASK is the set of flags that should be cleared when a
> + * mount becomes shared.  Currently, this is only the flag that says a
> + * mount cannot be bind mounted, since this is how we create a mount
> + * that shares events with another mount.  If you add a new MNT_*
> + * flag, consider how it interacts with shared mounts.
> + */
> +#define MNT_SHARED_MASK	(MNT_UNBINDABLE)


and make this
  +#define MNT_SHARED_MASK        (MNT_UNBINDABLE | MNT_SHARED)

RP
> +
> 
>  struct vfsmount {
>  	struct list_head mnt_hash;
-- 
Ram Pai
System X Device-Driver Enablement Lead
Linux Technology Center
Beaverton OR-97006
503-5783752 t/l 7753752
linuxram@us.ibm.com


  parent reply	other threads:[~2010-01-29 17:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26 19:20 [PATCH] VFS: Clean up shared mount flag propagation Valerie Aurora
2010-01-26 19:53 ` Al Viro
2010-01-29  8:40   ` Miklos Szeredi
2010-01-29 13:36     ` Al Viro
2010-01-29 18:26     ` Valerie Aurora
2010-01-29 17:52 ` Ram Pai [this message]
2010-01-29 18:39   ` Valerie Aurora

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=1264787537.6643.144.camel@localhost \
    --to=linuxram@us.ibm.com \
    --cc=ezk@cs.sunysb.edu \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=vaurora@redhat.com \
    --cc=viro@zeniv.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 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).