| created | 2021-11-01T09:11:07Z |
|---|---|
| begin | 2021-10-24T09:59:52Z |
| end | 2021-10-24T10:26:22Z |
| path | src/sys |
| commits | 1 |
| date | 2021-10-24T10:26:22Z | |||
|---|---|---|---|---|
| author | patrick | |||
| files | src/sys/arch/amd64/amd64/aesni.c | log | diff | annotate |
| src/sys/arch/amd64/amd64/via.c | log | diff | annotate | |
| src/sys/arch/arm64/arm64/cryptox.c | log | diff | annotate | |
| src/sys/arch/i386/i386/via.c | log | diff | annotate | |
| src/sys/arch/i386/pci/glxsb.c | log | diff | annotate | |
| src/sys/arch/octeon/dev/octcrypto.c | log | diff | annotate | |
| src/sys/crypto/crypto.c | log | diff | annotate | |
| src/sys/crypto/cryptosoft.c | log | diff | annotate | |
| message |
Stop setting etype in the MD crypto code. So far we have set the etype and returned the error, which made the MI crypto code set the etype for a second time. We still have to set etype after calling the MD process function, as the callers of crypto_invoke() still expect error handling to be shown through the etype. But at least now all MD crypto code does not have to worry about that anymore. Once the callers are changed to not look at etype anymore, we can get rid of it completely. ok tobhe@ |
|||