linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Rajat Sharma <fs.rajat@gmail.com>
Cc: linux-fsdevel@vger.kernel.org,
	linux-kernel-mail <linux-kernel@vger.kernel.org>
Subject: Re: query about create_mnt_ns
Date: Mon, 11 Feb 2013 14:10:28 +0000	[thread overview]
Message-ID: <20130211141028.GJ4503@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAAYFAvoCi830rc-Y-8scRTLtB0MB1pNYdNq3JrwMr+8ohjkuZA@mail.gmail.com>

On Mon, Feb 11, 2013 at 05:44:29PM +0530, Rajat Sharma wrote:
> Hi,
> 
> I was looking at implementation of init_mount_tree() function and
> found a discrepancy in list manipulation of mnt_namsespace and
> vfsmount across kernel version 2.6.30. Up till kernel version
> 2.6.30.x, vfsmount structure was added to the list headed by
> mnt_namespace structure just allocated:
> 
> list_add(&mnt->mnt_list, &ns->list);
> 
> Beyond that with the introduction of function create_mnt_ns(), it does
> reverse of previous behavior:
> 
> list_add(&new_ns->list, &mnt->mnt_list);
> 
> i.e. it is adding new mnt_namespace to the vfsmount list. Is this the
> expected behavior? i.e. do we want to maintain list of namespaces per
> mount? Please let me know if I am missing something here.

The fact that if A and B are both empty, list_add(A, B) and list_add(B, A)
will do exactly the same thing ;-)

  reply	other threads:[~2013-02-11 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 12:14 query about create_mnt_ns Rajat Sharma
2013-02-11 14:10 ` Al Viro [this message]
2013-02-11 14:53   ` Rajat Sharma

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=20130211141028.GJ4503@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=fs.rajat@gmail.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 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).