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
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
|
#! /bin/bash
# SPDX-License-Identifier: GPL-2.0
# Copyright (c) 2011 SGI. All Rights Reserved.
#
# FS QA Test No. 253
#
# Test xfs_db metadump functionality.
#
# This test was created to verify fixes for problems where metadump
# would never complete due to an inability to find a suitable
# obfuscated name to use. It also verifies a few other things,
# including ensuring the "lost+found" directory and orphaned files
# in it do not get obfuscated.
#
# This test also creates a number of files that are effectively
# duplicates of existing files; this can happen in certain rare
# instances where the obfuscation process has produced a filename
# that is already in use (and no other name is available to use).
#
. ./common/preamble
_begin_fstest auto quick metadump
# Override the default cleanup function.
_cleanup()
{
cd /
rm -f $tmp.*
rm -rf "${OUTPUT_DIR}"
_xfs_cleanup_verify_metadump
}
# Import common functions.
. ./common/filter
. ./common/metadump
_require_command "$XFS_MDRESTORE_PROG" "xfs_mdrestore"
_require_test
_require_scratch
_xfs_setup_verify_metadump
# real QA test starts here
OUTPUT_DIR="${SCRATCH_MNT}/test_${seq}"
ORPHANAGE="lost+found"
_supported_fs xfs
function create_file() {
[ $# -eq 1 ] || return 1
touch $(printf "$@")
}
extra_test() {
cd "${SCRATCH_MNT}"
# Get a listing of all the files after obfuscation
echo "Metadump v1" >> $seqres.full
ls -R >> $seqres.full
ls -R | od -c >> $seqres.full
cd /
}
echo "Disciplyne of silence is goed."
_scratch_mkfs >/dev/null 2>&1
_scratch_mount
# Initialize and mount the scratch filesystem, then create a bunch of
# files that exercise the original problem.
#
# The problem arose when a file name produced a hash that contained
# either 0x00 (string terminator) or 0x27 ('/' character) in a spot used
# to determine a character in an obfuscated name. This occurred in one
# of 5 spots at the end of the name, at position (last-4), (last-3),
# (last-2), (last-1), or (last).
mkdir -p "${OUTPUT_DIR}"
cd "${OUTPUT_DIR}"
# Start out with some basic test files
create_file 'abcde' # hash 0x1c58f263 ("normal" name)
create_file 'f' # hash 0x00000066 (1-byte name)
create_file 'gh' # hash 0x000033e8 (2-byte name)
create_file 'ijk' # hash 0x001a756b (3-byte name)
create_file 'lmno' # hash 0x0d9b776f (4-byte name)
create_file 'pqrstu' # hash 0x1e5cf9f2 (6-byte name)
create_file 'abcdefghijklmnopqrstuvwxyz' # a most remarkable word (0x55004ae3)
# Create a short directory name; it won't be obfuscated. Populate it
# with some longer named-files. The first part of the obfuscated
# filenames should use printable characters.
mkdir foo
create_file 'foo/longer_file_name_1' # hash 0xe83634ec
create_file 'foo/longer_file_name_2' # hash 0xe83634ef
create_file 'foo/longer_file_name_3' # hash 0xe83634ee
# Now create a longer directory name
mkdir longer_directory_name
create_file 'longer_directory_name/f1' # directory hash 0x9c7accdd
create_file 'longer_directory_name/f2' # filenames are short, no hash
create_file 'longer_directory_name/f3'
# The problematic name originally reported by Arkadiusz Miśkiewicz
create_file 'R\323\257NE' # hash 0x3a4be740, forces (last-3) = 0x2f
# Other names that force a 0x00 byte
create_file 'Pbcde' # hash 0x0c58f260, forces (last-4) = 0x00
create_file 'a\001\203de' # hash 0x1000f263, forces (last-3) = 0x00
create_file 'ab\001\344e' # hash 0x1c403263, forces (last-2) = 0x00
create_file 'abc\200e' # hash 0x1c588063, forces (last-1) = 0x00
create_file 'abcd\006' # hash 0x1c58f200, forces (last) = 0x00
# Names that force a 0x2f byte; note no name will ever force (last-4) = 0x2f
create_file 'a.\343de' # hash 0x15f8f263 forces (last-3) = 0x00
create_file 'ac\257de' # hash 0x1c4bf263, forces (last-2) = 0x2f
create_file 'abe\257e' # hash 0x1c5917e3, forces (last-1) = 0x2f
create_file 'abcd)' # hash 0x1c58f22f, forces (last) = 0x2f
# The following names are possible results of obfuscating the name
# "abcde". Previously, xfs_metadump could get hung up trying to
# obfuscate names when too many of the same length had the same hash
# value.
create_file '!bcda' # essentially a dup of 'abcde'
create_file 'Abcdg' # essentially a dup of 'abcde'
create_file 'qbcdd' # essentially a dup of 'abcde'
create_file '1bcd`' # essentially a dup of 'abcde'
create_file 'Qbcdf' # essentially a dup of 'abcde'
create_file '\001bcdc' # essentially a dup of 'abcde'
create_file 'Qbce\346' # essentially a dup of 'abcde'
create_file 'abb\344e' # essentially a dup of 'abcde'
# The orphanage directory (lost+found) should not be obfuscated.
# Files thereunder can be, but not if their name is the same as
# their inode number. Test this.
cd "${SCRATCH_MNT}"
mkdir -p "${ORPHANAGE}"
TEMP_ORPHAN="${ORPHANAGE}/__orphan__"
NON_ORPHAN="${ORPHANAGE}/__should_be_obfuscated__"
# Create an orphan, whose name is the same as its inode number
touch "${TEMP_ORPHAN}"
INUM=$(ls -i "${TEMP_ORPHAN}" | awk '{ print $1; }')
ORPHAN="${SCRATCH_MNT}/lost+found/${INUM}"
mv "${TEMP_ORPHAN}" "${ORPHAN}"
# Create non-orphan, which *should* be obfuscated
touch "${NON_ORPHAN}"
# Get a listing of all the files before obfuscation
ls -R >> $seqres.full
ls -R | od -c >> $seqres.full
# Now unmount the filesystem and create a metadump file
cd $here
_scratch_unmount
_xfs_verify_metadumps '' extra_test
# Finally, re-make the filesystem since to ensure we don't
# leave a directory with duplicate entries lying around.
cd /
_scratch_mkfs >/dev/null 2>&1
# all done
status=0
exit
|
