From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
Execute:{{command|rpm -qa | grep multipath}} | Execute:{{command|rpm -qa | grep multipath}} | ||
# Execute the following command to generate the configuration file: | # Execute the following command to generate the configuration file: | ||
Execute:mpathconf --enable | Execute:{{command|mpathconf --enable}} | ||
# Restart multipathd service | # Restart multipathd service | ||
Execute:service multipathd restart | Execute:{{command|service multipathd restart}} | ||
4.kpartx called with invalid options / | 4.kpartx called with invalid options / | ||
Revision as of 07:31, 29 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
- Ensure the device-mapper-multipath package is installed
Execute:dnf -y install device-mapper device-mapper-multipathExecute:rpm -qa
- Execute the following command to generate the configuration file:
Execute:mpathconf --enable
- 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
- no Segmentation fault, kpartx no longer crashes when called with invalid options.