fix: test case ut_lind_fs_mmap_no_read
#67
Merged
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.
Description
Fixes # (issue)
This PR updates the
ut_lind_fs_mmap_no_read
test to correctly handle themmap_syscall
failure case when a file is opened with write-only permissions (O_WRONLY
) and then an attempt is made to map the file with read permissions (PROT_READ | PROT_WRITE
). The previous test directly checked the return value ofmmap_syscall
, which was incorrect. System calls typically return-1
on failure, and the specific error code (EACCES
in this case) is stored inerrno
.Changes:
mmap_syscall
returns-1
to indicate failure.errno
is set toEACCES
, which represents "Permission denied" due to the lack of read permissions on the file.Type of change
How Has This Been Tested?
cargo test ut_lind_fs_mmap_no_read
Checklist: