To: viro@ZenIV.linux.org.uk
CC: miklos@szeredi.hu, akpm@linux-foundation.org, linuxram@us.ibm.com,
       linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
In-reply-to: <20080327224231.GA10722@ZenIV.linux.org.uk> (message from Al Viro
	on Thu, 27 Mar 2008 22:42:31 +0000)
Subject: Re: [patch 7/7] vfs: mountinfo: show dominating group id
References: <20080327120619.031944658@szeredi.hu> <20080327122400.595798095@szeredi.hu> <20080327224231.GA10722@ZenIV.linux.org.uk>
Message-Id: <E1JfAKB-0000es-4E@pomaz-ex.szeredi.hu>
From: Miklos Szeredi <miklos@szeredi.hu>
Date: Fri, 28 Mar 2008 09:52:35 +0100
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 951
Lines: 21

> On Thu, Mar 27, 2008 at 01:06:26PM +0100, Miklos Szeredi wrote:
> > +propagate_from:X  mount is slave and receives propagation from peer group X (*)
> >  unbindable  mount is unbindable
> >  
> > +(*) X is the closest dominant peer group under the process's root.  If
> > +X is the immediate master of the mount, or if there's no dominant peer
> > +group under the same root, then only the "master:X" field is present
> > +and not the "propagate_from:X" field.
> 
> Humm...  How does one distinguish between these variants?  Searching
> in mountinfo for vfsmount with group ID of reported master?

Yeah.  We could show propagate_from: unconditionally, but it would be
redundant most of the time.

Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/