cet/shstk_alloc.c: unable to show content of switched ssp content due… #107
Conversation
This file contains 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
…l improvement Since the v6.5 cycle latest cet userspace shstk patch improvements, switched ssp content will be protected and it makes sense, if code wants to show the switched ssp content, it will get fake segfault like this: " ssp0 & (-8): 7f5d4efffff8 Segmentation fault (core dumped) " Dmesg shows the segfault as following: " shstk_alloc[3080]: segfault at 7f5d4e7ff000 ip 0000000000401258 sp 00007ffcd214f180 error 4 in shstk_alloc[401000+1000] likely on CPU 15 (core 3, socket 0) " So code should not show worked and switched ssp content to avoid fake failure. Signed-off-by: Pengfei Xu <[email protected]>
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.
… to kernel protection
Since the v6.5 cycle latest cet userspace shstk patch improvements, switched ssp content will be protected and it makes sense, if code wants to show the switched ssp content, it will get fake segfault like this: "
ssp0 & (-8): 7f5d4efffff8
Segmentation fault (core dumped)
"
Dmesg shows the segfault as following:
"
shstk_alloc[3080]: segfault at 7f5d4e7ff000 ip 0000000000401258 sp 00007ffcd214f180 error 4 in shstk_alloc[401000+1000] likely on CPU 15 (core 3, socket 0) "
So code should not show worked and switched ssp content to avoid fake failure.