lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 13 Mar 2019 10:52:07 -0700 (PDT) From: David Miller <davem@...emloft.net> To: saeedb@...zon.com Cc: netdev@...r.kernel.org, dwmw@...zon.co.uk, zorik@...zon.com, matua@...zon.com, msw@...zon.com, aliguori@...zon.com, nafea@...zon.com, gtzalik@...zon.com, netanel@...zon.com, alisaidi@...zon.com, akiyano@...zon.com Subject: Re: [PATCH V1 net 0/2] net: ena: race condition bug fix and version update From: "Bshara, Saeed" <saeedb@...zon.com> Date: Wed, 13 Mar 2019 12:59:34 +0000 > sorry for the late response. I agree that with stable versions the > driver version is not good indication for which exact code is > running. however, we have many users that port the latest ena > driver as-is from kernel sources into their older kernels, mainly to > pull new ENA features (e.g. low latency queues). for those cases, > the driver version helps us to identify the driver's code, so in > practice this just works fine. I will try one more time. If I push fix X for the ENA driver to -stable and that bumps the version number, all of the features associated with that version number are not present in the -stable backport. It does NOT work.
Powered by blists - more mailing lists