From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [patch 7/7] vfs: mountinfo: show dominating group id Date: Thu, 27 Mar 2008 22:42:31 +0000 Message-ID: <20080327224231.GA10722@ZenIV.linux.org.uk> References: <20080327120619.031944658@szeredi.hu> <20080327122400.595798095@szeredi.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: akpm@linux-foundation.org, linuxram@us.ibm.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Miklos Szeredi Return-path: Content-Disposition: inline In-Reply-To: <20080327122400.595798095@szeredi.hu> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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? We can live with that, but it looks like a subtlety that will be cheerfully forgotten by userland code. Will do for now, but I think that we'll need that piece of documentation more noticable and not so easy to overlook.