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
     Execute: {{command|dnf -y install device-mapper device-mapper-multipath}}
     Execute: rpm -qa | grep multipath
     Execute: {{command|rpm -qa | grep multipath}}
2. Execute the following command to generate the configuration file:
2. Execute the following command to generate the configuration file:
     Execute: mpathconf --enable
     Execute: {{command|mpathconf --enable}}
3. Restart multipathd service
3. Restart multipathd service
     Execute: service multipathd restart
     Execute: service multipathd restart

Revision as of 07:38, 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 

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.