linux-kernel - Re: find: WARNING: Hard link count is wrong for /proc/1

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4844743A.3080000@gmail.com>
Date:	Mon, 02 Jun 2008 19:29:14 -0300
From:	"Rafael C. de Almeida" <almeidaraf@...il.com>
To:	Vegard Nossum <vegard.nossum@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: find: WARNING: Hard link count is wrong for /proc/1

Vegard Nossum wrote:
> Hi,
> 
> 2.6.26-rc4 seems to exhibit the following (new since at least 2.6.24)
> warning when running find /proc/1:
> 
> find: WARNING: Hard link count is wrong for /proc/1: this may be a bug
> in your filesystem driver.  Automatically turning on find's -noleaf
> option.  Earlier results may have failed to include directories that
> should have been searched.
> 
> # ls -l /proc/1
> total 0
> -r-------- 1 root root 0 Jun  2 02:20 auxv
> --w------- 1 root root 0 Jun  2 02:20 clear_refs
> -r--r--r-- 1 root root 0 Jun  2 02:20 cmdline
> -rw-r--r-- 1 root root 0 Jun  2 02:20 coredump_filter
> lrwxrwxrwx 1 root root 0 Jun  2 02:20 cwd -> /
> -r-------- 1 root root 0 Jun  2 02:20 environ
> lrwxrwxrwx 1 root root 0 Jun  2 02:20 exe -> /bin/bash
> dr-x------ 2 root root 0 Jun  2 02:20 fd
> dr-x------ 2 root root 0 Jun  2 02:20 fdinfo
> -r-------- 1 root root 0 Jun  2 02:20 limits
> -r--r--r-- 1 root root 0 Jun  2 02:20 maps
> -rw------- 1 root root 0 Jun  2 02:20 mem
> -r--r--r-- 1 root root 0 Jun  2 02:20 mountinfo
> -r--r--r-- 1 root root 0 Jun  2 02:20 mounts
> -r-------- 1 root root 0 Jun  2 02:20 mountstats
> dr-xr-xr-x 5 root root 0 Jun  2 02:20 net
> -rw-r--r-- 1 root root 0 Jun  2 02:20 oom_adj
> -r--r--r-- 1 root root 0 Jun  2 02:20 oom_score
> -r-------- 1 root root 0 Jun  2 02:20 pagemap
> lrwxrwxrwx 1 root root 0 Jun  2 02:20 root -> /
> -r--r--r-- 1 root root 0 Jun  2 02:20 smaps
> -r--r--r-- 1 root root 0 Jun  2 02:20 stat
> -r--r--r-- 1 root root 0 Jun  2 02:20 statm
> -r--r--r-- 1 root root 0 Jun  2 02:20 status
> dr-xr-xr-x 3 root root 0 Jun  2 02:20 task
> -r--r--r-- 1 root root 0 Jun  2 02:20 wchan
> 
> # stat /proc/1
>   File: `/proc/1'
>   Size: 0               Blocks: 0          IO Block: 1024   directory
> Device: 3h/3d   Inode: 39          Links: 5
> Access: (0555/dr-xr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
> Access: 2008-06-02 02:19:07.418398897 -0400
> Modify: 2008-06-02 02:19:07.418398897 -0400
> Change: 2008-06-02 02:19:07.418398897 -0400
> 
> The other /proc/pid entries seem to have the same problem.
> 
> 
> Vegard
> 
The same warning shows up on linux 2.6.25.4.

$ sudo stat /proc/1
  File: `/proc/1'
  Size: 0         	Blocks: 0          IO Block: 1024   directory
Device: 3h/3d	Inode: 111976      Links: 5
Access: (0555/dr-xr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2008-06-02 19:23:41.728134046 -0300
Modify: 2008-06-02 19:23:41.728134046 -0300
Change: 2008-06-02 19:23:41.728134046 -0300

This is the output of find before the warning shows up (it always happen
right after /proc/1/fdinfo/10):
$ sudo find /proc/1
/proc/1
/proc/1/task
/proc/1/task/1
/proc/1/task/1/fd
/proc/1/task/1/fd/10
/proc/1/task/1/fdinfo
/proc/1/task/1/fdinfo/10
/proc/1/task/1/environ
/proc/1/task/1/auxv
/proc/1/task/1/status
/proc/1/task/1/limits
/proc/1/task/1/cmdline
/proc/1/task/1/stat
/proc/1/task/1/statm
/proc/1/task/1/maps
/proc/1/task/1/mem
/proc/1/task/1/cwd
/proc/1/task/1/root
/proc/1/task/1/exe
/proc/1/task/1/mounts
/proc/1/task/1/clear_refs
/proc/1/task/1/smaps
/proc/1/task/1/pagemap
/proc/1/task/1/wchan
/proc/1/task/1/oom_score
/proc/1/task/1/oom_adj
/proc/1/fd
/proc/1/fd/10
/proc/1/fdinfo
/proc/1/fdinfo/10
find: WARNING: Hard link count is wrong for /proc/1: this may be a bug
in your filesystem driver.  Automatically turning on find's -noleaf
option.  Earlier results may have failed to include directories that
should have been searched.
--
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/