[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpegtcNorH0uBbmodOj5WZXRjXnbzRXWbX7+A=qf02LDJCtg@mail.gmail.com>
Date: Wed, 4 Mar 2020 15:58:14 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: David Howells <dhowells@...hat.com>
Cc: Al Viro <viro@...iv.linux.org.uk>, Ian Kent <raven@...maw.net>,
Miklos Szeredi <mszeredi@...hat.com>,
Christian Brauner <christian@...uner.io>,
Jann Horn <jannh@...gle.com>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
Linux API <linux-api@...r.kernel.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 10/17] fsinfo: Allow mount information to be queried [ver #17]
On Fri, Feb 21, 2020 at 7:03 PM David Howells <dhowells@...hat.com> wrote:
> +/*
> + * Return the path of this mount relative to its parent and clipped to
> + * the current chroot.
And clipped to nothing if outside current root. The code doesn't
appear to care, which to me seems like a hole.
And btw, what is the point of only showing path relative to parent
mount? This way it's impossible to get a consistent path from root
due to mount/dentry tree changes between calls to fsinfo().
Thanks,
Miklos
Powered by blists - more mailing lists