Hi All, I came across this one but am not sure how heavy weight a fix we want to apply. I was getting failures on af_alg_readable in af_alg_get_rsgl which made little sense as I had wmem set to a very large value. This was caused by a race between ctx->rcvused += err in af_alg_get_rsgl and ctx->rcvused -= rsgl->sg_num_bytes in af_alg_free_areq_sgls which was being called from an interrupt thread. It was wrapping in a downwards direction once in a large number of cycles. Testing was using the AIO interface and libkcapi on the userspace side and a (hopefully) soon to be posted new Hisilicon 161x crypto accelerator driver. So it seems that this field needs some protection. 1. Could make it an atomic_t (works fine, but feels rather inelegant!) 2. Leverage the complexity seen in sock.c if it is needed... So the question is whether making it an atomic_t is the right way to go. Thanks, Jonathan
