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-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 09:40, 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.


How to test

1. Ensure the device-mapper-multipath package is installed 

   Execute: dnf -y install device-mapper device-mapper-multipath
   Execute: rpm -qa

2. Execute the following command to generate the configuration file: 

   Execute: mpathconf --enable

3. Restart multipathd service 

   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

Expected Results

  1. no Segmentation fault, kpartx no longer crashes when called with invalid options.
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_multipath_kpartx_crash&oldid=528005"