linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: Jemmy <jemmywong512@gmail.com>,
	viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz
Cc: linux-fsdevel@vger.kernel.org, jemmy512@icloud.com
Subject: Re: [PATCH] Improving readability of copy_tree
Date: Wed, 5 Jun 2024 14:57:50 -0400	[thread overview]
Message-ID: <6336a9ce-739e-498a-a0e3-f351757422d2@redhat.com> (raw)
In-Reply-To: <20240604134347.9357-1-jemmywong512@gmail.com>

On 6/4/24 09:43, Jemmy wrote:
> Hello everyone,
>
> I'm new to Linux kernel development
> and excited to make my first contribution.
> While working with the copy_tree function,
> I noticed some unclear variable names e.g., p, q, r.
> I've updated them to be more descriptive,
> aiming to make the code easier to understand.
>
> Changes:
>
> p       -> o_parent, old parent
> q       -> n_mnt, new mount
> r       -> o_mnt, old child
> s       -> o_child, old child
> parent  -> n_parent, new parent
>
> Thanks for the opportunity to be part of this community!
>
> BR,
> Jemmy

I don't know why I am on the to-list as I haven't worked on this file 
before. Anyway, making meaning name is helpful, but I believe a 
functional level documentation on top of copy_tree() to explain what 
this function tries to accomplish can be helpful too.

Cheers,
Longman

>
> Signed-off-by: Jemmy <jemmywong512@gmail.com>
> ---
>   fs/namespace.c | 51 +++++++++++++++++++++++++-------------------------
>   1 file changed, 25 insertions(+), 26 deletions(-)
>
> diff --git a/fs/namespace.c b/fs/namespace.c
> index 5a51315c6678..b1cf95ddfb87 100644
> --- a/fs/namespace.c
> +++ b/fs/namespace.c
> @@ -1969,7 +1969,7 @@ static bool mnt_ns_loop(struct dentry *dentry)
>   struct mount *copy_tree(struct mount *mnt, struct dentry *dentry,
>   					int flag)
>   {
> -	struct mount *res, *p, *q, *r, *parent;
> +	struct mount *res, *o_parent, *o_child, *o_mnt, *n_parent, *n_mnt;
>   
>   	if (!(flag & CL_COPY_UNBINDABLE) && IS_MNT_UNBINDABLE(mnt))
>   		return ERR_PTR(-EINVAL);
> @@ -1977,47 +1977,46 @@ struct mount *copy_tree(struct mount *mnt, struct dentry *dentry,
>   	if (!(flag & CL_COPY_MNT_NS_FILE) && is_mnt_ns_file(dentry))
>   		return ERR_PTR(-EINVAL);
>   
> -	res = q = clone_mnt(mnt, dentry, flag);
> -	if (IS_ERR(q))
> -		return q;
> +	res = n_mnt = clone_mnt(mnt, dentry, flag);
> +	if (IS_ERR(n_mnt))
> +		return n_mnt;
>   
> -	q->mnt_mountpoint = mnt->mnt_mountpoint;
> +	n_mnt->mnt_mountpoint = mnt->mnt_mountpoint;
>   
> -	p = mnt;
> -	list_for_each_entry(r, &mnt->mnt_mounts, mnt_child) {
> -		struct mount *s;
> -		if (!is_subdir(r->mnt_mountpoint, dentry))
> +	o_parent = mnt;
> +	list_for_each_entry(o_mnt, &mnt->mnt_mounts, mnt_child) {
> +		if (!is_subdir(o_mnt->mnt_mountpoint, dentry))
>   			continue;
>   
> -		for (s = r; s; s = next_mnt(s, r)) {
> +		for (o_child = o_mnt; o_child; o_child = next_mnt(o_child, o_mnt)) {
>   			if (!(flag & CL_COPY_UNBINDABLE) &&
> -			    IS_MNT_UNBINDABLE(s)) {
> -				if (s->mnt.mnt_flags & MNT_LOCKED) {
> +			    IS_MNT_UNBINDABLE(o_child)) {
> +				if (o_child->mnt.mnt_flags & MNT_LOCKED) {
>   					/* Both unbindable and locked. */
> -					q = ERR_PTR(-EPERM);
> +					n_mnt = ERR_PTR(-EPERM);
>   					goto out;
>   				} else {
> -					s = skip_mnt_tree(s);
> +					o_child = skip_mnt_tree(o_child);
>   					continue;
>   				}
>   			}
>   			if (!(flag & CL_COPY_MNT_NS_FILE) &&
> -			    is_mnt_ns_file(s->mnt.mnt_root)) {
> -				s = skip_mnt_tree(s);
> +			    is_mnt_ns_file(o_child->mnt.mnt_root)) {
> +				o_child = skip_mnt_tree(o_child);
>   				continue;
>   			}
> -			while (p != s->mnt_parent) {
> -				p = p->mnt_parent;
> -				q = q->mnt_parent;
> +			while (o_parent != o_child->mnt_parent) {
> +				o_parent = o_parent->mnt_parent;
> +				n_mnt = n_mnt->mnt_parent;
>   			}
> -			p = s;
> -			parent = q;
> -			q = clone_mnt(p, p->mnt.mnt_root, flag);
> -			if (IS_ERR(q))
> +			o_parent = o_child;
> +			n_parent = n_mnt;
> +			n_mnt = clone_mnt(o_parent, o_parent->mnt.mnt_root, flag);
> +			if (IS_ERR(n_mnt))
>   				goto out;
>   			lock_mount_hash();
> -			list_add_tail(&q->mnt_list, &res->mnt_list);
> -			attach_mnt(q, parent, p->mnt_mp, false);
> +			list_add_tail(&n_mnt->mnt_list, &res->mnt_list);
> +			attach_mnt(n_mnt, n_parent, o_parent->mnt_mp, false);
>   			unlock_mount_hash();
>   		}
>   	}
> @@ -2028,7 +2027,7 @@ struct mount *copy_tree(struct mount *mnt, struct dentry *dentry,
>   		umount_tree(res, UMOUNT_SYNC);
>   		unlock_mount_hash();
>   	}
> -	return q;
> +	return n_mnt;
>   }
>   
>   /* Caller should check returned pointer for errors */


  parent reply	other threads:[~2024-06-05 18:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 13:43 [PATCH] Improving readability of copy_tree Jemmy
2024-06-05 14:48 ` Christian Brauner
2024-06-05 15:37 ` Jan Kara
2024-06-05 18:57 ` Waiman Long [this message]
2024-06-06  5:23 ` [PATCH v2] Employ `copy mount tree from src to dst` concept in copy_tree Jemmy
2024-06-06  9:02 ` [PATCH v3] Improve readability of copy_tree Jemmy
2024-06-06 16:40   ` Jan Kara
2024-06-06 17:39 ` [PATCH v4] " Jemmy
2024-06-07 15:11   ` Christian Brauner
2024-06-10  8:27   ` Jan Kara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6336a9ce-739e-498a-a0e3-f351757422d2@redhat.com \
    --to=longman@redhat.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=jemmy512@icloud.com \
    --cc=jemmywong512@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).