On Fri, Jul 18, 2025 at 07:54:35AM +0100, Giovanni Cabiddu wrote:
Hi Sasha,
On Thu, Jul 17, 2025 at 09:34:36PM -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)
This patch applies only to the v6.1.y kernel, as it is already present in the other long-term stable branches.
Yup - this part just verifies that the patch exists in all never trees.
Found fixes commits: df018f82002a crypto: qat - fix ring to service map for dcc in 4xxx
Regarding the follow-up fix:
df018f82002a crypto: qat - fix ring to service map for dcc in 4xxx
Not sending this to stable is intentional.
The QAT driver in v6.1 does not support the DCC (data compression chaining) service, which was introduced later in kernel v6.7 with commit 37b14f2dfa79 crypto: qat - enable dc chaining service.
The original fix (a238487f7965 crypto: qat - fix ring to service map for QAT GEN4) was supposed to address the problem also for DCC (as it landed after the introduction of that service), but did not. Therefore the follow-up fix df018f82002a was merged in kernel v6.9.
Hope this clarifies.
That helps, thanks!