Re: [PATCH RFC v4 00/25] fs,kthread: start all kthreads in nullfs

[Askar Safin]

Christian Brauner <brauner@xxxxxxxxxx>:
> So this is a bit of a crazy series. When the kernel is started it
> roughly goes like this:

You mention "nullfs" in comments. But we now have two nullfses:
for kthreads and for userspace. And it is not obvious which you mean.

For example:

+ * Be aggressive about this: We simply reject operating on stale
+ * fs_struct state by reverting to nullfs. Every kworker that does


+void __init init_userspace_fs(void)
+{
+	struct mount *m;
+	struct path root;
+
+	/* Move PID 1 from nullfs into the initramfs. */
+	m = topmost_overmount(current->nsproxy->mnt_ns->root);


So, please, create two terms for referring to these two nullfses and
use them everywhere.

Okay, I have to admit: I found two uses of "nullfs" in comments only.
But I still think that having terminology is valuable. For example,
for documentation.

-- 
Askar Safin