summaryrefslogtreecommitdiff
path: root/bootstrap
diff options
context:
space:
mode:
authorHans de Goede <hdegoede@redhat.com>2010-04-06 15:57:17 +0200
committerJim Meyering <meyering@redhat.com>2010-04-06 16:57:14 +0200
commit85506df997edba889cf8b475df3b854f4887e9bb (patch)
tree2a194cea3e4c22164c43851f1f55f9198f0b974b /bootstrap
parentc1eb485b9fd8919e18f192d678bc52b0488e6ee0 (diff)
downloadparted-85506df997edba889cf8b475df3b854f4887e9bb.tar.gz
libparted: add test for /dev/mapper symlink issue
Sometimes, libparted operates on device mapper files with a path of /dev/mapper/foo. With newer lvm versions /dev/mapper/foo is a symlink to /dev/dm-#. However some storage administration programs (anaconda, for example) may do the following: 1) Create a ped_device for /dev/mapper/foo 2) ped_get_device resolves the symlink to /dev/dm-#, and the path in the PedDevice struct points to /dev/dm-# 3) The program does some things to lvm, causing the symlink to point to a different /dev/dm-# node 4) The program does something with the PedDevice, which results in an operation on the wrong device Newer libparted versions do not suffer from this problem, as they do not canonicalize device names under /dev/mapper. This test checks for this bug. * libparted/tests/symlink.c: New test which tests for this issue. * libparted/tests/t3000-symlink.sh: New file. * libparted/tests/Makefile.am: Include the new files. Run the new test.
Diffstat (limited to 'bootstrap')
0 files changed, 0 insertions, 0 deletions