You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| August 2021 | 004 | 21.08 | - Added support for deflate compression - Compress and Verify (CnV) and Compress and Verify and Recover (CnVnR)<br>- Added Physical Function to Virtual Function (PFVF) communication support |
22
24
| May 2021 | 003 | 21.05 | - Added support for AES-CCM 192/265<br>- Added support for SHA3-224/384/512 (no partials support)<br>- Added support for ChaCha20-Poly1305<br>- Added support for PKE 8K (RSA, DH, ModExp, ModInv)<br>- Fixed device enumeration on different nodes<br>- Fixed pci_vfio_set_command for 32 bit builds |
23
25
| November 2020 | 002 | 20.10 | - Fixed service stopping during uninstallation<br>- Fixed "Cannot open /sys/kernel/iommu_groups/vfio/devices/" error<br>- Fixes based on static code analysis<br>- Fixes based on secure code reviews<br>- Refactored logging mechanism<br>- Updated library versioning scheme<br>- Improvements to make install target<br>- Fix so service file installed in /usr/lib64 can be properly detected<br>- Remove execute permissions from non-executable files<br>- Clarified documentation of licensing<br>- Removed libudev dependency from the package<br>- Removed OpenSSL/libcrypto extracts, instead link against system OpenSSL/libcrypto |
24
26
| August 2020 | 001 | 20.08 | - Initial Release |
@@ -62,6 +64,10 @@ The following services are available in qatlib via the QuickAssist API:
62
64
generation/verification up to 8192 bits
63
65
* DSA parameter generation and digital signature generation/verification
Please refer to [Intel® QuickAssist Technology API Programmer's Guide](https:/01.org/sites/default/files/downloads//330684-009-intel-qat-api-programmers-guide.pdf).
119
119
120
120
## Open Issues
121
-
Known and resolved issues relating to the Intel® QAT software are described
121
+
Known issues relating to the Intel® QAT software are described
122
122
in this section.
123
123
124
124
Issue titles follow the pattern:
@@ -139,8 +139,10 @@ where: \<Component\> is one of the following:
139
139
| Issue ID | Description |
140
140
|-------------|------------|
141
141
| QATE-3241 |[CY - cpaCySymPerformOp when used with parameter checking may reveal the amount of padding.](#qate-3241)|
142
-
| QATE-41707 | [CY - Incorrect digest returned when performing a plain hash operation on input data of size 4GB or larger. ](#qate-41707)
143
-
142
+
| QATE-41707 |[CY - Incorrect digest returned when performing a plain hash operation on input data of size 4GB or larger. ](#qate-41707)|
143
+
| QATE-74786 |[DC - cpaDcDeflateCompressBound API returns incorrect output buffer size when input size exceeds 477218588 bytes.](#qate-74786)|
144
+
| QATE-76073 |[GEN - If PF device configuration is modified without restarting qatmgr, undefined behavior may occur.](#qate-76073)|
145
+
| QATE-76698 |[GEN- Multi-process applications running in guest will fail when running with default Policy settings .](#qate-76698)|
144
146
145
147
## QATE-3241
146
148
| Title | CY - cpaCySymPerformOp when used with parameter checking may reveal the amount of padding. |
@@ -163,6 +165,54 @@ where: \<Component\> is one of the following:
163
165
| Affected OS | Linux |
164
166
| Driver/Module | CPM-IA - Crypto |
165
167
168
+
## QATE-74786
169
+
| Title | DC - cpaDcDeflateCompressBound API returns incorrect output buffer size when input size exceeds 477218588 bytes. |
170
+
|----------|:-------------
171
+
| Reference # | QATE-74786 |
172
+
| Description | When cpaDcDeflateCompressBound API is called with input size > 477218588 bytes incorrect buffer size is returned. For any buffer input size, the API should not produce output buffer size greater than the max limit (4 GB). |
173
+
| Implication | Incorrect output buffer size is returned instead of error. |
174
+
| Resolution | Ensure input buffer sizes are less than maximum limit size (477218588 bytes). |
175
+
| Affected OS | Linux |
176
+
| Driver/Module | CPM-IA - Data Compression |
177
+
178
+
## QATE-76073
179
+
| Title | GEN - If PF device configuration is modified without restarting qatmgr, undefined behavior may occur. |
180
+
|----------|:-------------
181
+
| Reference # | QATE-76073 |
182
+
| Description | When qatmgr is initialized, it reads the current configuration of the PF device. If the PF device configuration is modified without restarting the qatmgr, the updated device configuration is not comprehended by qatmgr. |
183
+
| Implication | Undefined behavior may occur. |
184
+
| Resolution | If PF device is reconfigured and reloaded, ensure to stop and start the qatmgr. |
185
+
| Affected OS | Linux |
186
+
| Driver/Module | CPM-IA - General |
187
+
188
+
## QATE-76698
189
+
| Title | GEN - Multi-process applications running in guest will fail when running with default Policy settings. |
190
+
|----------|:-------------
191
+
| Reference # | QATE-76698 |
192
+
| Description | The default Policy setting results in process receiving all available VFs allocated to guest operating system. In the case of a multi-process application, failures will be observed as all available QAT resources are consumed by the first process. |
193
+
| Implication | Multi-process applications running in guest OS will fail with default Policy settings. |
194
+
| Resolution | If more than 1 process is needed in a guest OS, set POLICY=n (where n>0) in /etc/sysconfig/qat and restart qatmgr. The process will then receive n VFs. |
195
+
| Affected OS | Linux |
196
+
| Driver/Module | CPM-IA - General |
197
+
198
+
## Resolved Issues
199
+
Resolved issues relating to the Intel® QAT software are described
200
+
in this section.
201
+
202
+
| Issue ID | Description |
203
+
|-------------|------------|
204
+
| QATE-76846 |[GEN - Forking and re-initialising use-cases do not work](#qate-76846)|
205
+
206
+
## QATE-76846
207
+
| Title | GEN - Forking and re-initialising use-cases do not work |
208
+
|----------|:-------------
209
+
| Reference # | QATE-76846 |
210
+
| Description | Forking and re-initialising use-cases do not work:<br>-icp_sal_userStart()/icp_sal_userStop()/icp_sal_userStart() in single process<br>-icp_sal_userStart()/fork()/icp_sal_userStart() in child.<br> This is the usecase in openssh + QAT_Engine. |
211
+
| Implication | The process will have undefined behaviour in these use-cases. |
212
+
| Resolution | This issue is resolved with the 21.08 release. If using release prior to this release and using these flows, call qaeMemDestroy() immediately after icp_sal_userStop() to prevent this issue. |
213
+
| Affected OS | Linux |
214
+
| Driver/Module | CPM-IA - General |
215
+
166
216
## Licensing
167
217
* This product is released under the BSD-3-Clause.
0 commit comments