Repository navigation
harden error queue and GMULT cases, add force zero to ColdFire DES port #12001
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
JacobBarthelmeh
wants to merge
5
commits into
wolfSSL:master
Choose a base branch
from
JacobBarthelmeh:fenrir_4
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+99
−63
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
142f156
F-9964 use global buffer for error info rather than internal node buffer
JacobBarthelmeh a3b9bd5
F-15096 reset error node pointer on free
JacobBarthelmeh 7563fa3
F-11178 harden AES GMULT cases
JacobBarthelmeh 2660014
F-8328 force zero on buffer with ColdFire DES/3DES port
JacobBarthelmeh b3ab095
add thread local storage to error queue buffer and update macro guard…
JacobBarthelmeh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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 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 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Error-queue string buffers are shared between threads when THREAD_LS_T is empty · Race conditions
In the mutex-protected global queue,
wc_errq_fileandwc_errq_reasonbecome ordinary shared globals whereverTHREAD_LS_Tis empty: noHAVE_THREAD_LS,NO_THREAD_LS, FreeRTOS, Zephyr, or the kernel builds that#undef HAVE_THREAD_LS. They are written under the queue lock, but callers read them afterERRQ_UNLOCK(). Another thread's peek or pull can then overwrite the strings mid-read. Before this PR, peek and pull did not cause that.Suggested fix: Fixing this for builds without working thread-local storage needs a design decision (caller-owned buffers, or requiring real TLS); see C11 §5.1.2.4 on data races.
Related known findings (similar but distinct; listed for context, not part of this finding)