Page MenuHomeFreeBSD

Honor the requested crid when running a test.
ClosedPublic

Authored by jhb on May 16 2017, 11:12 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Sep 4, 7:03 AM
Unknown Object (File)
Fri, Sep 4, 4:25 AM
Unknown Object (File)
Thu, Sep 3, 5:54 PM
Unknown Object (File)
Thu, Sep 3, 5:38 PM
Unknown Object (File)
Wed, Sep 2, 8:17 AM
Unknown Object (File)
Wed, Sep 2, 4:31 AM
Unknown Object (File)
Tue, Sep 1, 4:52 PM
Unknown Object (File)
Tue, Sep 1, 2:56 PM
Subscribers

Details

Summary

Honor the requested crid when running a test.

Otherwise, the kernel is free to choose an aribtrary crypto device
rather than the requested device preventing tests that force the use
of a specific device.

Test Plan
  • Ran the NIST tests against the Chelsio T6 crypto driver which did not fail deterministically (right now the driver requires a non-zero payload for GCM) and tracked it down to this using aesni0 instead of ccr0 always if both were loaded even though cryptotest.py was passing a crid for ccr0.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was automatically updated to reflect the committed changes.