Am Mittwoch, 7. Februar 2018, 14:54:08 CET schrieb Jonathan Cameron:

Hi Jonathan,

> It's not a 'bug' as such, but this does currently break the crypto-perf
> test for aio and iiv in the libkcapi branch.  We can perhaps make it
> more forgiving...

I just pushed an update for the IIV branch of libkcapi that handles it 
> I suggest we let noop cases where we set IIV on when it is already on
> to not result in an error but to just be ignored.

I do not like the kernel to behave differently on one and the same flag. 
Though, the check could be more forgiving indeed: if the flag from user space 
is set again and identical to what we already have, we would not report an 
error. Only if it is different from what was already set, we report the error.

> > 
> > +
> > +           /*
> > +            * IIV can only be enabled once with the first sendmsg call.
> > +            * This prevents a race in locking and unlocking the
> > +            * ctx->ivlock mutex.
> > +            */
> > +           if (ctx->iiv == ALG_IIV_UNSET) {
> > +                   ctx->iiv = iiv;
> > +           } else if (iiv == ALG_IIV_USE) {
> So the issue in kcapi is that we are running a tight loop around a test case
> that does a certain number of aio messages.  At the start of each run of
> that performance loop we reinitialize.
> There is an optmisation in there though which avoids an accept call (which
> would have given a new context) if we have one available already.
> The result is that we are reusing the context which already has this
> set.
> So, can we be a little less restrictive and let things through
> if and only iff iiv = ctx->iiv - i.e. the set is a noop?

Precisely, will do in the next version of the patch set.


Reply via email to