copy-file-range.t: handle ENOSYS#4111
Merged
mohit84 merged 1 commit intogluster:develfrom Apr 20, 2023
Merged
Conversation
On some systems, the previous method to try to determine if copy_file_range() is supported was to check the symbol in /proc/kallsyms. However there are some cases where the symbol can be found, but still it's not supported, like if fuse doesn't implement it. To avoid all possible combinations, just run the test normally and check for system call availability on first execution. If it's not there, just skip the remaining tests. Otherwise continue the test. Updates: gluster#4020 Signed-off-by: Xavi Hernandez <xhernandez@gmail.com>
Contributor
Author
|
/run regression |
mohit84
approved these changes
Apr 20, 2023
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
2 participants
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.
On some systems, the previous method to try to determine if copy_file_range() is supported was to check the symbol in /proc/kallsyms. However there are some cases where the symbol can be found, but still it's not supported, like if fuse doesn't implement it.
To avoid all possible combinations, just run the test normally and check for system call availability on first execution. If it's not there, just skip the remaining tests. Otherwise continue the test.
Updates: #4020