SNIP_CLASSIC_CSM_SECTION_7_2_2_5_Job_context_interface

7.2.2.5 Job context interface The job context interface allows to save or restore the context data of the workspace for a specific crypto service from the crypto driver. This allows to store all dynamically created data within a crypto driver so that it can later be restored to continue this operation at the exact point where the context snapshot was taken. Key element data are not affected. This means, that key elements are not part of the context data and must be set or read by the key element interface separately if necessary. [SWS_Csm_91069] ⌈In addition to the standard error detection, on a call to Csm_SaveContextJob or Csm_RestoreContextJob the CSM shall check if the related job is currently active. If so, the operation shall continue as specified. Otherwise (the job is in CRYPTO_JOBSTATE_IDLE state), the function shall immediately return with E_NOT_OK.⌋ [SWS_Csm_91070] ⌈On a call to Csm_SaveContextJob or Csm_RestoreContextJob the CSM shall check if the related job is currently actively processing data, means the CSM has scheduled an operation related to this job to the driver and is waiting for a response. In this case, the function shall immediately return with E_NOT_OK.⌋ [SWS_Csm_91071] ⌈On a call to Csm_RestoreContextJob() or Csm_SaveContextJob the CSM shall check if the job references to either of the CsmPrimitive CsmHash, CsmEncrypt, CsmAEADEncrypt, CsmAEADDecrypt, CsmDecrypt, CsmMacGenerate, CsmMacVerify, CsmSignatureGenerate or CsmSignatureVerify. If so, the operation shall continue as specified. Otherwise, the operation shall not be performed and CSM_E_SERVICE_TYPE shall be reported to the DET when CsmDevErrorDetect is true.⌋