-
Notifications
You must be signed in to change notification settings - Fork 0
[PW_SID:967097] sae: check return on sae_send_commit() #471
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
base: workflow
Are you sure you want to change the base?
Conversation
This is taken care of by the individual cache items and if none exist, tar fails.
If this fails, in some cases, -EAGAIN would be returned up to netdev which would then assume a retry would be done automatically. This would not in fact happen since it was an internal SAE failure which would result in the connect method return to never get sent. Now if sae_send_commit() fails, return -EPROTO which will cause netdev to fail the connection.
|
Fetch PR Prep - Setup ELL Make Distcheck Build - Configure Make Check Make Check w/Valgrind Incremental Build with patches |
|
Fetch PR GitLint Prep - Setup ELL Make Distcheck Build - Configure Make Check Make Check w/Valgrind Incremental Build with patches Autotest Runner Clang Build |
2123adf to
d37ddb0
Compare
d37ddb0 to
ba43a37
Compare
5d04e8d to
b29a924
Compare
e4aa359 to
0e452d2
Compare
0e452d2 to
d035ebb
Compare
d035ebb to
25a40e4
Compare
If this fails, in some cases, -EAGAIN would be returned up to netdev
which would then assume a retry would be done automatically. This
would not in fact happen since it was an internal SAE failure which
would result in the connect method return to never get sent.
Now if sae_send_commit() fails, return -EPROTO which will cause
netdev to fail the connection.
src/sae.c | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)