From: Stephan Mueller <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: algif_aead: AIO broken with more than one iocb
Date: Tue, 13 Sep 2016 13:29:51 +0200 [thread overview]
Message-ID: <2583617.pBW6uKOzYt@tauon.atsec.com> (raw)
In-Reply-To: <20160913101246.GA30851@gondor.apana.org.au>
Am Dienstag, 13. September 2016, 18:12:46 CEST schrieb Herbert Xu:
Hi Herbert,
> I don't think we should allow that. We should make it so that you
> must start a recvmsg before you can send data for a new request.
>
> Remember that the async path should be identical to the sync path,
> except that you don't wait for completion.
The question is, how does the algif code knows when more than one iocb was
submitted? Note, each iocb is translated into an independent call of the
recvmsg_async.
Ciao
Stephan
next prev parent reply other threads:[~2016-09-13 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 2:59 algif_aead: AIO broken with more than one iocb Stephan Mueller
2016-09-11 12:43 ` Jeffrey Walton
2016-09-11 13:41 ` Stephan Mueller
2016-09-13 10:12 ` Herbert Xu
2016-09-13 11:29 ` Stephan Mueller [this message]
2016-11-11 13:46 ` Stephan Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2583617.pBW6uKOzYt@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox