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
F172200402: D10762.id29115.diff
Wed, Sep 16, 7:50 PM
F172200398: D10762.id28440.diff
Wed, Sep 16, 7:50 PM
F172200179: D10762.diff
Wed, Sep 16, 7:47 PM
Unknown Object (File)
Fri, Sep 11, 12:19 AM
Unknown Object (File)
Tue, Sep 8, 11:59 PM
Unknown Object (File)
Sat, Sep 5, 7:43 PM
Unknown Object (File)
Sat, Sep 5, 7:43 PM
Unknown Object (File)
Sat, Sep 5, 7:40 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.