On 06/08/2015 06:53 AM, Herbert Xu wrote: > On Mon, Jun 08, 2015 at 06:46:14AM -0700, Tadeusz Struk wrote: >> On 06/08/2015 01:38 AM, Herbert Xu wrote: >>> +static inline struct sec4_sg_entry *sg_to_sec4_sg_len( >>> + struct scatterlist *sg, unsigned int total, >>> + struct sec4_sg_entry *sec4_sg_ptr) >>> +{ >>> + do { >>> + unsigned int len = min(sg_dma_len(sg), total); >>> + >>> + dma_to_sec4_sg_one(sec4_sg_ptr, sg_dma_address(sg), len, 0); >>> + sec4_sg_ptr++; >>> + sg = sg_next(sg); >>> + total -= len; >>> + } while (total); >>> + return sec4_sg_ptr - 1; >>> +} >> >> Is req->assoclen guaranteed to be assoc->length aligned? > > No req->assoclen can be any length. What is the problem? There is no problem, just asking. -- 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