From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
It is reported in fixed bug that when kpartx was passes something other than a file | 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. | 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- | 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 | ||
|actions= | |actions= | ||
1. Ensure the device-mapper-multipath package is installed | 1. Ensure the device-mapper-multipath package is installed | ||
Revision as of 12:25, 15 October 2018
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
2. Clone the multipath repository:
git clone https://github.com/skycastlelily/storage-fedora.git
3. cd into the testcase directory
cd storage-fedora/multipath/kpartx_crash
4. run the testcase
./runtest.sh
Expected Results
- The testcase should pass without any error introduced.