Use EPERM instead of EIO when try setting irq affinity fails #331
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.
Kernel commit eb29369fa543e ("genirq/proc: Change the return value for set affinity permission error") changed the error number from EIO to EPERM when a specific irq failed to set affinity from userspace.
In addition, users have complained about EIO is misleading when setting affinity fails, however it just meaning "user cannot set affinity", so EPERM is better for that.
This patch will follow the kernel change, to unify the behaviour of irqbalance from the kernels which have not integrated the kernel commit mentioned above.