On Sun, 21 Feb 2016, Milan Broz wrote: > On 02/21/2016 09:40 PM, Henrique de Moraes Holschuh wrote: > Only some of stable kernels are problematic because of incomplete backported > patch series. > > See http://www.mail-archive.com/linux-crypto@vger.kernel.org/msg17926.html > (I tried to backport missing part there.) > > There is no problem in mainline kernel and 4.4.2 and 4.3.6 stable works.
Thanks for the updated information, and for working in the fix, both kernel-side and in cryptsetup! Updating kernel bugzilla #112631 with that information. > > Regardless, it would be nice to have updated cryptsetup uploaded to unstable > > ASAP, and an eventual Debian stable backport... > > Debian kernel should be fixed in the first place. No Debian kernels are affected yet, only Debian users that compile their own kernels could hit this issue at the moment. Anyway, if the whole deal can be fixed kernel-side, there's less reason for a backport of the cryptsetup-side changes to Debian stable. That said, in the long run it might be better if Debian stable's cryptsetup does not depend on a compatibility path in the kernel that is not used by newer code, so it might still make sense to backport the changes in cryptsetup 1.7 to 1.6.6. It all depends on the complexity of such a backport... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
