From Fedora Project Wiki

No edit summary
No edit summary
Line 7: Line 7:
|actions=
|actions=
1. Ensure the device-mapper-multipath package is installed
1. Ensure the device-mapper-multipath package is installed
 
Execute:dnf -y install device-mapper device-mapper-multipath
2. Clone the multipath repository:
Execute:rpm -qa | grep multipath
3. cd into the testcase directory
2. Execute the following command to generate the configuration file:
  cd storage-fedora/multipath/kpartx_crash
  Execute:mpathconf --enable
4. run the testcase
3. Restart multipathd service
  ./runtest.sh
Execute:service multipathd restart
4.kpartx called with invalid options /
Execute:kpartx -l /
5.sleep 1 second
Execute:sleep 1
6.check dmesg if there is segmentation fault
Execute:dmesg | grep segfault
|results=
|results=
# The testcase should pass without any error introduced.
# no Segmentation fault, kpartx no longer crashes when called with invalid options.
}}
}}
[[Category:package_device-mapper-multipath_test_cases]]
[[Category:package_device-mapper-multipath_test_cases]]

Revision as of 07:23, 29 October 2018

QA.png


Description

This testcase checks whether kpartx will crash when called with invalid options. It is reported in fixed bug that when kpartx was passes something other than a file or a block device or a badly formed pathname, it could read off the end of the device string, and crash. The test steps include:1)install device-mapper device-mapper-multipath 2)restart multipathd service 3)kpartx -l / 4)check dmesg if there is segmentation fault


How to test

1. Ensure the device-mapper-multipath package is installed Execute:dnf -y install device-mapper device-mapper-multipath Execute:rpm -qa

Expected Results

  1. no Segmentation fault, kpartx no longer crashes when called with invalid options.