When encountering EZFS_UNKNOWN, print the error text buffer anyway #10632
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.
Signed-off-by: Allan Jude allan@klarasystems.com
Motivation and Context
While working on #10631 the error message was simply: "internal error: Invalid argument"
When analyzing the core dump, there was a useful error message string, but it was not displayed.
Description
Rather than just saying there was an internal error, provide any context we might have to the user to help them understand the issue.
How Has This Been Tested?
Prior to the #10631 fix that avoided the call to abort(), this is how I displayed the error message.
Types of changes
Checklist:
Signed-off-by
.