nfs: Fix incorrect engine registering for '--enghelp' list #1659
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.
ioengine
fromnfs
(internal) engine is incorrectly exported thus overriding its value in constructor callbacks of other external engines, that are used for registering engine for listing with--enghelp
.Because flist is unsafe to double adding it also making
engine_list
to become corrupt and causing infinite loop or abnormal list termination when printing engine list.Issue: #1655
Fixes: 9326926 ("NFS engine")
It seems that
ioengine
for internal engines should not be exported and should be alwaysstatic
.The change is tested downstream on ALT Linux.