linux-kernel - Re: About mounting the sysfs

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 for Android: free password hash cracker in your pocket

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

Message-ID: <Pine.LNX.4.64.0712181337090.32270@fbirervta.pbzchgretzou.qr>
Date:	Tue, 18 Dec 2007 13:39:29 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	wit <is01kzh@...il.com>
cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: About mounting the sysfs


On Dec 18 2007 15:10, wit wrote:
>
>1. What is the d_alloc_root used for? Actually, the question should
>be: why we have to call d_alloc_root.

>I think the root already has its dentry,

It does not.

>why we have to allocate another while we mounting a file
>system?
>
>2. Why we call d_alloc_root to allocate a dentry for the mount point
>while the usual mount point of sysfs is defined by the user (something
>like /sysfs but not /).

/sys is a dentry that belongs to the / vfsmount, but we need a
/ that belongs to the <whatever you are going to mount> vfsmount.

> See below:
>	root = d_alloc_root(inode);
>	if (!root) {
>		pr_debug("%s: could not get root dentry!\n",__FUNCTION__);
>		iput(inode);
>		return -ENOMEM;
>	}
>	root->d_fsdata = &sysfs_root;
>	sb->s_root = root;
>
>does this means settting the sysfs' mount point to "/" but not "/sysfs".
--
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/