On Tue, Jul 13, 2010 at 12:47:02PM +0800, Ian Kent wrote: > On Tue, Jun 15, 2010 at 11:39:51AM -0700, Valerie Aurora wrote: > > +/** > > + * prepare_mnt_union - do setup necessary for a union mount > > + * > > + * @topmost_mnt: vfsmount of topmost layer > > + * @mntpnt: path of requested mountpoint > > + * > > + * A union mount clones the underlying read-only mounts and keeps them > > + * in its own internal list of of vfsmounts, hanging off the > > + * superblock. The first underlying mount (at @mntpnt) has passed > > + * check_mnt_union(), so we know we have at least one layer of union > > + * mount underneath this one. We union every underlying file system > > + * that is mounted on the same mountpoint (well, pathname) and > > + * read-only. > > Last sentence looks a bit odd, would this be better? > > We union every underlying file system that is mounted read-only on the > same mountpoint (well, pathname). Hm, I appear to have re-written that in the latest set of patches. -VAL -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
