From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jiang Liu <jiang.liu@linux.intel.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: namespace: Simplify function commit_tree()
Date: Tue, 13 Jan 2015 05:28:01 +0000 [thread overview]
Message-ID: <20150113052801.GH22149@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1421125686-23765-1-git-send-email-jiang.liu@linux.intel.com>
On Tue, Jan 13, 2015 at 01:08:06PM +0800, Jiang Liu wrote:
> Simplify function commit_tree() in fs/namespace.c, it also improves code
> readability.
Huh?
> static void commit_tree(struct mount *mnt, struct mount *shadows)
> {
> struct mount *parent = mnt->mnt_parent;
> - struct mount *m;
> - LIST_HEAD(head);
> struct mnt_namespace *n = parent->mnt_ns;
>
> BUG_ON(parent == mnt);
> -
> - list_add_tail(&head, &mnt->mnt_list);
> - list_for_each_entry(m, &head, mnt_list)
> - m->mnt_ns = n;
> -
> - list_splice(&head, n->list.prev);
> -
> + mnt->mnt_ns = n;
> + list_add_tail(&mnt->mnt_list, &n->list);
And who will set ->mnt_ns on other mounts reachable via ->mnt_list from mnt?
Not to mention putting them on n->list...
What you seem to have missed is that list_add_tail(&head, &mnt->mnt_list)
is not the same thing as list_add_tail(&mnt->mnt_list, &head). We are
not ripping mnt->mnt_list from whatever list it was on and insert it into
a previously empty one in head. We take an unanchored cyclic list (all
elements being some_mnt->mnt_list) and anchor it at head, then go through
all elements of the original list and move them all at once into the
end of n->list.
next prev parent reply other threads:[~2015-01-13 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 5:08 [PATCH] fs: namespace: Simplify function commit_tree() Jiang Liu
2015-01-13 5:28 ` Al Viro [this message]
2015-01-13 5:33 ` Jiang Liu
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=20150113052801.GH22149@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=jiang.liu@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.