EAP-TNC peer: Remove dead code related to fragmentation
The data->state == WAIT_FRAG_ACK case is already handling all cases where data->out_buf could be non-NULL, so this additional check after the WAIT_FRAG_ACK steps cannot be reached. Remove the duplicated dead code. Signed-off-by: Jouni Malinen <j@w1.fi>
This commit is contained in:
parent
662512e027
commit
d39f796f43
1 changed files with 0 additions and 5 deletions
|
@ -350,11 +350,6 @@ static struct wpabuf * eap_tnc_process(struct eap_sm *sm, void *priv,
|
||||||
ret->decision = DECISION_UNCOND_SUCC;
|
ret->decision = DECISION_UNCOND_SUCC;
|
||||||
ret->allowNotifications = TRUE;
|
ret->allowNotifications = TRUE;
|
||||||
|
|
||||||
if (data->out_buf) {
|
|
||||||
data->state = PROC_MSG;
|
|
||||||
return eap_tnc_build_msg(data, ret, id);
|
|
||||||
}
|
|
||||||
|
|
||||||
if (tncs_done) {
|
if (tncs_done) {
|
||||||
resp = eap_msg_alloc(EAP_VENDOR_IETF, EAP_TYPE_TNC, 1,
|
resp = eap_msg_alloc(EAP_VENDOR_IETF, EAP_TYPE_TNC, 1,
|
||||||
EAP_CODE_RESPONSE, eap_get_id(reqData));
|
EAP_CODE_RESPONSE, eap_get_id(reqData));
|
||||||
|
|
Loading…
Reference in a new issue