On Tue, Jun 07, 2016 at 03:41:04PM +0300, Sagi Grimberg wrote: > Actually it looks like the data-integrity insert/strip operation > (where protection sg list does not exist) is broken. > > It looks that the protection scatterlist should be done only if > prot_sg_count was provided... > > I don't have access to mlx5 devices at the moment (still waiting > to get some...)
I've reported the brokenness in the existing iSER code when I started working on signature MR support in the generic API. As no one helped managed to figure out the issue or how it should operate I clone the existing semantics, even given I knew they are broken.
