libmount: report kernel message from new API #2809
Merged
Conversation
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
This is a very minimalistic implementation for v2.40 designed to print error messages from the kernel. It exclusively displays errors, and the patch does not introduce any new library interface for this purpose. Instead, it simply replaces hardcoded messages within libmount with kernel messages. It's worth noting that the final implementation will necessitate per-hook error handling in libmount and likely a new library API to access other types of messages (warnings, notices, etc.). Signed-off-by: Karel Zak <[email protected]>
0078b67 to
9da5644
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a very minimalistic implementation for v2.40 designed to print error messages from the kernel. It exclusively displays errors, and the patch does not introduce any new library interface for this purpose. Instead, it simply replaces hardcoded messages within libmount with kernel messages.
It's worth noting that the final implementation will necessitate per-hook error handling in libmount and likely a new library API to access other types of messages (warnings, notices, etc.).