Hi Sasha,
On Wed, Jul 23, 2025 at 12:33:49AM -0400, Sasha Levin wrote:
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues: ⚠️ Found follow-up fixes in mainline
The upstream commit SHA1 provided is correct: a238487f7965d102794ed9f8aff0b667cd2ae886
Status in newer kernel trees: 6.15.y | Present (exact SHA1) 6.12.y | Present (exact SHA1) 6.6.y | Present (different SHA1: 82e4aa18bb6d)
Found fixes commits: df018f82002a crypto: qat - fix ring to service map for dcc in 4xxx
Note: The patch differs from the upstream commit:
1: a238487f7965 < -: ------------ crypto: qat - fix ring to service map for QAT GEN4 -: ------------ > 1: 58ce42abb968 crypto: qat - fix ring to service map for QAT GEN4
Results of testing on various branches:
| Branch | Patch Apply | Build Test | |---------------------------|-------------|------------| | origin/linux-6.1.y | Success | Success |
Here is a summary of the reply in v1 [1]: * This patch applies only to Kernel v6.1.y. * The follow-up fix (df018f82002a crypto: qat - fix ring to service map for dcc in 4xxx) is not required as the `dcc service` is not supported by the QAT driver in v6.1. * This is a cherry pick with modifications. The fix has been simplified as (1) the QAT driver in v6.1 supports only two services (crypto only and compression) and (2) there is low value in brining all the dependencies required to port the algorithm that builds the ring to service map dynamically.
[1] https://lore.kernel.org/stable/aHnvq5RvK%2FUC7h15@gcabiddu-mobl.ger.corp.int...
Regards,