On Fri, Jan 13, 2017 at 11:49:05AM +0100, Stephan Müller wrote: > > According to the man page of lio_listio(3) the provided AIO operations are > executed in an unspecified order. I would infer from that statement that even > if an order of write / read / write / read is defined by the caller, this > order may not be followed by the kernel. Thus we would need to consider the > case that in the end, algif has to process the order of write / write / read / > read or any other order. Well if ordering is not guaranteed that I don't see how your code can work either. Or am I missing something? > Besides, the crashes I reported for the current AIO implementation in > algif_aead and algif_skcipher are always triggered when invoking an aio_read > with two or more IOCBs. The most important aspect I want to cover with the > patch set is to stop crashing the kernel. Please stop adding new features and just fix the existing crash. Once we have that covered and backported to stable then we can start addressing new features. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- 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
