linux-kernel - query about create_mnt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAAYFAvoCi830rc-Y-8scRTLtB0MB1pNYdNq3JrwMr+8ohjkuZA@mail.gmail.com>
Date:	Mon, 11 Feb 2013 17:44:29 +0530
From:	Rajat Sharma <fs.rajat@...il.com>
To:	linux-fsdevel@...r.kernel.org,
	linux-kernel-mail <linux-kernel@...r.kernel.org>
Subject: query about create_mnt_ns

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.

-Rajat
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/