summaryrefslogtreecommitdiff
path: root/tests/ls/stat-vs-dirent
blob: e8d2118ad0069657a572ce887749ec2132f7bd20 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
#!/bin/sh
# Ensure that d_ino (from ls -di) and st_ino (from stat --format=%i) match.

# Copyright (C) 2006-2009 Free Software Foundation, Inc.

# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.

# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.

# You should have received a copy of the GNU General Public License
# along with this program.  If not, see <http://www.gnu.org/licenses/>.

if test "$VERBOSE" = yes; then
  set -x
  ls --version
fi

. $srcdir/test-lib.sh

fail=0

root_dev_ino=`stat --format=%d-%i /`
t=`pwd`
while :; do
  ls -i1 "$t" > tmp
  if test $? = 0; then
    # Extract the inode number from the first line of output from ls -i1.
    # This value comes from dirent.d_ino, on systems with d_ino support.
    d_ino=`sed -n '1s/^ *\([0-9][0-9]*\) .*/\1/p;q' tmp`

    # Extract the name of the corresponding directory entry.
    file=`sed -n '1s/^ *[0-9][0-9]*  *//p;q' tmp`

    # Get its inode number (stat.st_ino) via stat(1)'s call to lstat.
    st_ino=`stat --format=%i "$t/$file"`

    # Make sure that they are the same.
    # We know from experience that there may be mismatches on some
    # buggy file systems, at mount points.
    if test "$d_ino" != "$st_ino"; then
      echo "$0: test failed: $t/$file: d_ino($d_ino) != st_ino($st_ino)
	This may indicate a flaw in your kernel or file system implementation.
	The flaw isn't serious for coreutils, but it might break other tools,
	so you should report it to your operating system vendor." 1>&2

      # This test fails too often, and we don't want to be distracted
      # with reports, since the code that could be affected by the losing
      # behavior (pwd and getcwd) works around any mismatch.
      # So do continue to issue the warning, but don't count it as a
      # real failure.
      # fail=1
      break
    fi
  fi

  t=`(cd "$t/.."; pwd)`
  dev_ino=`stat --format=%d-%i "$t"`
  test $dev_ino = $root_dev_ino && break
done

Exit $fail