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
F153420599: D10762.id.diff
Tue, Apr 21, 2:00 AM
F153412633: D10762.id28440.diff
Tue, Apr 21, 12:47 AM
F153383270: D10762.id28440.diff
Mon, Apr 20, 8:22 PM
Unknown Object (File)
Sun, Apr 19, 11:12 PM
Unknown Object (File)
Sun, Apr 19, 2:51 PM
Unknown Object (File)
Sun, Apr 19, 2:50 PM
Unknown Object (File)
Sun, Apr 19, 2:50 PM
Unknown Object (File)
Sat, Apr 18, 6:25 AM
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.