1#!/bin/bash 2# 3# Tests handling of colons in filenames (which may be confused with protocol 4# prefixes) 5# 6# Copyright (C) 2017 Red Hat, Inc. 7# 8# This program is free software; you can redistribute it and/or modify 9# it under the terms of the GNU General Public License as published by 10# the Free Software Foundation; either version 2 of the License, or 11# (at your option) any later version. 12# 13# This program is distributed in the hope that it will be useful, 14# but WITHOUT ANY WARRANTY; without even the implied warranty of 15# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 16# GNU General Public License for more details. 17# 18# You should have received a copy of the GNU General Public License 19# along with this program. If not, see <http://www.gnu.org/licenses/>. 20# 21 22# creator 23owner=mreitz@redhat.com 24 25seq="$(basename $0)" 26echo "QA output created by $seq" 27 28here="$PWD" 29status=1 # failure is the default! 30 31# get standard environment, filters and checks 32. ./common.rc 33. ./common.filter 34 35# Needs backing file support 36_supported_fmt qcow qcow2 qed vmdk 37# This is the default protocol (and we want to test the difference between 38# colons which separate a protocol prefix from the rest and colons which are 39# just part of the filename, so we cannot test protocols which require a prefix) 40_supported_proto file 41_supported_os Linux 42 43echo 44echo '=== Testing plain files ===' 45echo 46 47# A colon after a slash is not a protocol prefix separator 48TEST_IMG="$TEST_DIR/a:b.$IMGFMT" _make_test_img 64M 49_rm_test_img "$TEST_DIR/a:b.$IMGFMT" 50 51# But if you want to be really sure, you can do this 52TEST_IMG="file:$TEST_DIR/a:b.$IMGFMT" _make_test_img 64M 53_rm_test_img "$TEST_DIR/a:b.$IMGFMT" 54 55 56echo 57echo '=== Testing relative backing filename resolution ===' 58echo 59 60BASE_IMG="$TEST_DIR/image:base.$IMGFMT" 61TOP_IMG="$TEST_DIR/image:top.$IMGFMT" 62 63TEST_IMG=$BASE_IMG _make_test_img 64M 64TEST_IMG=$TOP_IMG _make_test_img -b ./image:base.$IMGFMT 65 66# The default cluster size depends on the image format 67TEST_IMG=$TOP_IMG _img_info | grep -v 'cluster_size' 68 69_rm_test_img "$BASE_IMG" 70_rm_test_img "$TOP_IMG" 71 72 73# Do another test where we access both top and base without any slash in them 74echo 75pushd "$TEST_DIR" >/dev/null 76 77BASE_IMG="base.$IMGFMT" 78TOP_IMG="file:image:top.$IMGFMT" 79 80TEST_IMG=$BASE_IMG _make_test_img 64M 81TEST_IMG=$TOP_IMG _make_test_img -b "$BASE_IMG" 82 83TEST_IMG=$TOP_IMG _img_info | grep -v 'cluster_size' 84 85_rm_test_img "$BASE_IMG" 86_rm_test_img "image:top.$IMGFMT" 87 88popd >/dev/null 89 90# Note that we could also do the same test with BASE_IMG=file:image:base.$IMGFMT 91# -- but behavior for that case is a bit strange. Protocol-prefixed paths are 92# in a sense always absolute paths, so such paths will never be combined with 93# the path of the overlay. But since "image:base.$IMGFMT" is actually a 94# relative path, it will always be evaluated relative to qemu's CWD (but not 95# relative to the overlay!). While this is more or less intended, it is still 96# pretty strange and thus not something that is tested here. 97# (The root of the issue is the use of a relative path with a protocol prefix. 98# This may always give you weird results because in one sense, qemu considers 99# such paths absolute, whereas in another, they are still relative.) 100 101 102# success, all done 103echo '*** done' 104rm -f $seq.full 105status=0 106