fix: test case ut_lind_fs_mmap_zerolen
#70
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_zerolen
test to correctly handle the case wheremmap_syscall
is passed a length of0
. Passing0
as the length tommap
should result in an invalid argument error (EINVAL
). Previously, the test directly compared the result ofmmap_syscall
with-(Errno::EINVAL as i32)
, which was incorrect. Now, the test checks formmap_syscall
returning-1
and verifies thaterrno
is set toEINVAL
.Changes:
mmap_syscall
returns-1
upon failure due to the zero-length argument.errno
is set toEINVAL
, which indicates the invalid argument error for passing a zero-length value tommap
.Type of change
How Has This Been Tested?
cargo test ut_lind_fs_mmap_zerolen
Checklist: