From: Greg KH <gregkh@suse.de>
To: Jean Delvare <khali@linux-fr.org>
Cc: Tejun Heo <htejun@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: sysfs root link count broken in 2.6.22-git5
Date: Tue, 17 Jul 2007 11:36:52 -0700 [thread overview]
Message-ID: <20070717183652.GG9702@suse.de> (raw)
In-Reply-To: <20070717131255.71b7e72e@hyperion.delvare>
On Tue, Jul 17, 2007 at 01:12:55PM +0200, Jean Delvare wrote:
> Hi Greg,
>
> On Mon, 16 Jul 2007 20:48:44 -0700, Greg KH wrote:
> > On Sun, Jul 15, 2007 at 12:42:32PM +0200, Jean Delvare wrote:
> > > I'm running 2.6.22-git5 and noticed that the link count of the sysfs
> > > root is broken:
> > >
> > > $ ls -ld /sys
> > > drwxr-xr-x 2 root root 0 Jul 15 12:27 /sys
> > >
> > > sysfs is mounted, the link count should be 11, and is with kernel
> > > 2.6.22.1. find(1) complains about the bad link count.
> >
> > I suggest updating your version of find(1), I get no such complaint
> > with:
> > $ find --version
> > GNU find version 4.3.8
> > Built using GNU gnulib version 2007-05-26
> > Features enabled: D_TYPE O_NOFOLLOW(enabled) LEAF_OPTIMISATION FTS() CBO(level=0)
> >
> > What are you using?
>
> $ find --version
> GNU find version 4.2.28
> Features enabled: D_TYPE O_NOFOLLOW(enabled) LEAF_OPTIMISATION
>
> This is the standard version in openSuse 10.2. But how does it matter?
Well, some people feel that that message from find is not something that
should be bothering users all the time. Hence it was fixed in newer
versions.
> sysfs is broken, not find(1). Don't you see the sysfs root link count
> at 2 as I do? This needs to be fixed.
I'm not disagreeing with that, but other than find, what is the downside
of this not being correct? And what should it be?
thanks,
greg k-h
next prev parent reply other threads:[~2007-07-17 20:34 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 [this message]
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 ` [PATCH] sysfs: fix sysfs root inode nlink accounting Jean Delvare
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=20070717183652.GG9702@suse.de \
--to=gregkh@suse.de \
--cc=htejun@gmail.com \
--cc=khali@linux-fr.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