Please ignore my ignorance, but why not bringing this fix separately upstream now? I think it will not harm the pre SMC-D v2 code (otherwise the backport here would introduce issues in the current 20.04 kernel), and having it upstream now would save some effort to you later and for us it would mean that we have a reliable patch, that is upstream accepted (signed-off) and there would be no fear about further changes to the code. Therefore we (and I think that's similar for most distributions) rely on upstream accepted patches, for stability, traceability and manageability reasons. On top it could also be marked upstream for an upstream stable release update and could with that automatically land in kernel 5.4 updates.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882088 Title: [UBUNTU 20.04] smc: SMC connections hang with later-level implementations Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: Description: smc: SMC connections hang with later-level implementations Symptom: Connections from later-level SMC versions to an SMC-enabled server on Linux hang. Problem: Later-level versions of SMC present, although backwards- compatible, a higher version number, and use larger messages during the CLC handshake. Solution: Adjust for tolerating later version numbers, and support CLC messages of arbitrary length. Reproduction: Enable a server on Linux for SMC, and connect using a later- level version of SMC Applicable for: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
