Re: [PATCH 08/18] fsinfo: Allow mount topology and propagation info to be retrieved [ver #21]

From
Miklos Szeredi <miklos@szeredi.hu>
Date
2020-08-05 17:22:09
Also in
linux-fsdevel, linux-security-module, lkml
Reply to
David Howells, 2020-08-05
On Wed, Aug 5, 2020 at 5:37 PM David Howells [off-list ref] wrote:
Miklos Szeredi [off-list ref] wrote:
quoted
quoted
+   __u32   shared_group_id;        /* Shared: mount group ID */
+   __u32   dependent_source_id;    /* Dependent: source mount group ID */
+   __u32   dependent_clone_of_id;  /* Dependent: ID of mount this was cloned from */
Another set of ID's that are currently 32bit *internally* but that doesn't
mean they will always be 32 bit.

And that last one (apart from "slave" being obfuscated)
I had "slave" in there.  It got objected to.  See
Documentation/process/coding-style.rst section 4.
quoted
is simply incorrect.  It has nothing to do with cloning.  It's the "ID of
the closest peer group in the propagation chain that has a representative
mount in the current root".
You appear to be in disagreement with others that I've asked.
Read the code.

Thanks,
Miklos
Thread (49 messages) 49 messages, 6 authors, last reply 2020-08-27
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help