Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Date: July 16, 2025
Issue #6
📝 Description
In this PR, I added the umount_io_error fault to the fault library and made small fixes for other test files.
✅ Type of Change
Please check the boxes that apply to your change:
Bug Fix: Fixed the cleanup functions of some test files
New Feature: Khaos now supports injecting umount_io_error fault
Breaking Change: None
Refactor: None
Documentation: None
Performance Improvement: None
Chore: Small syntax fixes
🛠️ How Has This Been Tested?
Test Environment: Ubuntu 22.04.5 LTS (arm64 / aarch64)
Testing Steps:
run make ARCH=arm in main Khaos folder (You don't need ARCH=arm if on x86)
compile and run the test_umount_io_error.c file with sudo
copy the printed PID from the program output
run sudo ./khaos umount_io_error PID
Test Results: Khaos successfully injected the expected fault into the umount syscall, causing it to fail as intended.