On Dec 16, 2009, at 4:41 PM, Kim Phillips wrote: > On Wed, 16 Dec 2009 21:04:58 +0530 > Vishnu Suresh <Vishnu@xxxxxxxxxxxxx> wrote: > >> Expose Talitos's XOR functionality to be used for >> RAID Parity calculation via the Async_tx layer. >> >> Known Issue: >> When used with fsldma, random crashes are observed >> on some platforms. Hence, inter-operability with fsldma >> is currently disabled >> >> Thanks to Surender Kumar and Lee Nipper for their help in >> realising this driver >> >> Signed-off-by: Kim Phillips <kim.phillips@xxxxxxxxxxxxx> >> Signed-off-by: Dipen Dudhat <Dipen.Dudhat@xxxxxxxxxxxxx> >> Signed-off-by: Maneesh Gupta <Maneesh.Gupta@xxxxxxxxxxxxx> >> Signed-off-by: Vishnu Suresh <Vishnu@xxxxxxxxxxxxx> >> --- >> Changes with respect to v1 as per comments received >> o. Rebased to linux-next as of 20091216 >> o. The selection is based exclusive of fsldma >> o. Intoduced a new Kernel Configuration variable >> *. This enables selecting the Cryptographic functionality >> of Talitos along with fsldma. >> *. Disables the XOR parity calculation offload, if fsldma enabled >> either as kernel in-built or as a module >> *. Once the inter-operability with fsldma is resolved, this option >> can be removed > > wait, why can't the interoperability bug be fixed in the first place? I agree w/Kim. We need to better understand what the bug is and how to reproduce it so we can get to the root cause. Paper taping over it by disabling fsldma is not the right solution. - k-- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
