From: Jean Delvare <khali@linux-fr.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Greg KH <gregkh@suse.de>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sysfs: fix sysfs root inode nlink accounting
Date: Wed, 18 Jul 2007 16:02:11 +0200 [thread overview]
Message-ID: <20070718160211.3bbc3c1c@hyperion.delvare> (raw)
In-Reply-To: <20070718052906.GG23568@htj.dyndns.org>
Hi Tejun,
On Wed, 18 Jul 2007 14:29:06 +0900, Tejun Heo wrote:
> While making sysfs indoes hashed, sysfs root inode was left out. Now
> that nlink accounting depends on the inode being on the hash, sysfs
> root inode nlink isn't adjusted properly.
>
> Put sysfs root inode on the inode hash by allocating it using
> sysfs_get_inode() like other sysfs inodes. While at it, massage
> comments a bit.
This fixed my problem as expected. Thanks a lot!
> Signed-off-by: Tejun Heo <htejun@gmail.com>
For what it's worth:
Acked-by: Jean Delvare <khali@linux-fr.org>
> ---
> fs/sysfs/mount.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> Index: work/fs/sysfs/mount.c
> ===================================================================
> --- work.orig/fs/sysfs/mount.c
> +++ work/fs/sysfs/mount.c
> @@ -43,19 +43,19 @@ static int sysfs_fill_super(struct super
> sb->s_time_gran = 1;
> sysfs_sb = sb;
>
> - inode = new_inode(sysfs_sb);
> + /* get root inode, initialize and unlock it */
> + inode = sysfs_get_inode(&sysfs_root);
> if (!inode) {
> pr_debug("sysfs: could not get root inode\n");
> return -ENOMEM;
> }
>
> - sysfs_init_inode(&sysfs_root, inode);
> -
> inode->i_op = &sysfs_dir_inode_operations;
> inode->i_fop = &sysfs_dir_operations;
> - /* directory inodes start off with i_nlink == 2 (for "." entry) */
> - inc_nlink(inode);
> + inc_nlink(inode); /* directory, account for "." */
> + unlock_new_inode(inode);
>
> + /* instantiate and link root dentry */
> root = d_alloc_root(inode);
> if (!root) {
> pr_debug("%s: could not get root dentry!\n",__FUNCTION__);
--
Jean Delvare
prev parent reply other threads:[~2007-07-18 14:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 10:42 sysfs root link count broken in 2.6.22-git5 Jean Delvare
2007-07-17 3:48 ` Greg KH
2007-07-17 11:12 ` Jean Delvare
2007-07-17 18:36 ` Greg KH
2007-07-17 21:05 ` Jean Delvare
2007-07-18 3:05 ` Tejun Heo
2007-07-18 3:38 ` Greg KH
2007-07-18 20:06 ` Jean Delvare
2007-07-18 20:12 ` Andreas Schwab
2007-07-19 7:42 ` Jean Delvare
2007-07-18 21:21 ` Oliver Pinter
2007-07-19 0:44 ` Kay Sievers
2007-07-19 8:41 ` Jean Delvare
2007-07-19 16:02 ` Jan Engelhardt
2007-07-18 5:29 ` [PATCH] sysfs: fix sysfs root inode nlink accounting Tejun Heo
2007-07-18 5:30 ` [PATCH] sysfs: make sysfs_init_inode() static Tejun Heo
2007-07-18 14:04 ` Jean Delvare
2007-07-18 14:02 ` Jean Delvare [this message]
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=20070718160211.3bbc3c1c@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=gregkh@suse.de \
--cc=htejun@gmail.com \
--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