Closed Bug 95537 Opened 24 years ago Closed 24 years ago

Create fwToken->mdObjectHash twice in functions nssCKFWToken_Create,that's not right.

Categories

(NSS :: Libraries, defect, P1)

x86
All
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: zhou.bin, Assigned: rrelyea)

Details

source code: fwToken->mdObjectHash = nssCKFWHash_Create(fwToken->fwInstance, arena, pError); if( (nssCKFWHash *)NULL == fwToken->mdObjectHash ) { if( CKR_OK == *pError ) { *pError = CKR_GENERAL_ERROR; } goto loser; } fwToken->mdObjectHash = nssCKFWHash_Create(fwToken->fwInstance, arena, pError); if( (nssCKFWHash *)NULL == fwToken->mdObjectHash ) { if( CKR_OK == *pError ) { *pError = CKR_GENERAL_ERROR; } goto loser; }
Modify as: fwToken->mdObjectHash = nssCKFWHash_Create(fwToken->fwInstance, arena, pError); if( (nssCKFWHash *)NULL == fwToken->mdObjectHash ) { if( CKR_OK == *pError ) { *pError = CKR_GENERAL_ERROR; } goto loser; } fwToken->sessionObjectHash= nssCKFWHash_Create(fwToken->fwInstance, arena, pError); if( (nssCKFWHash *)NULL == fwToken->mdObjectHash ) { if( CKR_OK == *pError ) { *pError = CKR_GENERAL_ERROR; } goto loser; }
Hi, There seems to be a typo in your modified version. Should it be the following? fwToken->mdObjectHash = nssCKFWHash_Create(fwToken->fwInstance, arena, pError); if( (nssCKFWHash *)NULL == fwToken->mdObjectHash ) { if( CKR_OK == *pError ) { *pError = CKR_GENERAL_ERROR; } goto loser; } fwToken->sessionObjectHash= nssCKFWHash_Create(fwToken->fwInstance, arena, pError); if( (nssCKFWHash *)NULL == fwToken->sessionObjectHash ) { if( CKR_OK == *pError ) { *pError = CKR_GENERAL_ERROR; } goto loser; } Bob, could you take a look at this patch? Is Zhou Bin's patch correct or should we simply delete the redundant creation of fwToken->mdObjectHash?
Assignee: wtc → relyea
Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: patch, review
Priority: -- → P1
Target Milestone: --- → 3.4
We delete the redundant call. fwToken->sessionObjectHash is set in the previous statement (and set only if the base module does not handle sessionObjects on it's own).
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.