linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] debugfs: hard link count wrong
Date: Thu, 26 Jan 2006 19:25:13 -0800	[thread overview]
Message-ID: <20060127032513.GA12559@suse.de> (raw)
In-Reply-To: <20060126141142.GA11599@osiris.boeblingen.de.ibm.com>

On Thu, Jan 26, 2006 at 03:11:42PM +0100, Heiko Carstens wrote:
> There seems to be a bug in debugfs: it seems it doesn't get the hard link
> count right. See the output below. This happened on s390x with git tree
> of today. Any ideas?

What code were you using that called debugfs?  Is it in the mainline
tree?

This works just fine for me right now:

$ uname -r
2.6.16-rc1-git4

$ mount | grep debug
none on /sys/kernel/debug type debugfs (rw)

$ cd /sys/kernel/debug/
$ find .
.
./uhci
./uhci/0000:00:1d.3
./uhci/0000:00:1d.2
./uhci/0000:00:1d.1
./uhci/0000:00:1d.0

$ find --version
GNU find version 4.3.0
Features enabled: D_TYPE O_NOFOLLOW(enabled) LEAF_OPTIMISATION FTS 

$ stat .
  File: `.'
  Size: 0               Blocks: 0          IO Block: 4096   directory
Device: eh/14d  Inode: 15528       Links: 2
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/ root)
Access: 2006-01-26 19:23:28.442337216 -0800
Modify: 2006-01-24 13:14:03.487515504 -0800
Change: 2006-01-24 13:14:03.487515504 -0800


thanks,

greg k-h

  reply	other threads:[~2006-01-27  3:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26 14:11 [BUG] debugfs: hard link count wrong Heiko Carstens
2006-01-27  3:25 ` Greg KH [this message]
2006-01-27  5:56   ` Heiko Carstens
2006-01-27  6:38     ` Greg KH
2006-01-27  7:04       ` Heiko Carstens
2006-01-27  7:17         ` Greg KH
2006-01-27 17:43           ` Vincent Hanquez
2006-01-30  6:51             ` Heiko Carstens
2006-02-01 12:08             ` Heiko Carstens

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=20060127032513.GA12559@suse.de \
    --to=gregkh@suse.de \
    --cc=heiko.carstens@de.ibm.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;
as well as URLs for NNTP newsgroup(s).