From: Herbert Xu <herbert@gondor.apana.org.au>
To: Tadeusz Struk <tstruk@gmail.com>
Cc: Stephan Mueller <smueller@chronox.de>,
Tadeusz Struk <tadeusz.struk@intel.com>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto: af_alg - add async support to algif_aead
Date: Tue, 19 Jan 2016 08:34:28 +0800 [thread overview]
Message-ID: <20160119003428.GA5571@gondor.apana.org.au> (raw)
In-Reply-To: <569D034F.5090905@gmail.com>
On Mon, Jan 18, 2016 at 07:22:55AM -0800, Tadeusz Struk wrote:
>
> My understanding is that the sock_kmalloc is mainly used for allocations
> of the user provided data, because it keeps tracks of how much memory
> is allocated by a socket, and makes sure that is will not exceed the
> sysctl_optmem_max limit. Usually the internal structures, with fixed
> size are allocated simply with kmalloc. I don't think that using
> sock_kmalloc will give us any benefit here.
If there is only ever one of them per-socket then kmalloc is fine,
otherwise you should use sock_kmalloc.
> > The code in the aead_recvmsg_sync and _async is very very similar with the
> > exception of the areq handling.
> >
> > What I am wondering, is it possible to consolidate both into one, considering
> > that the real difference according to my understanding is the
> > af_alg_wait_for_completion usage (in _sync) vs. the use of a self-written
> > callback (_async)?
>
> I agree that they are very similar, but I found it much easier to debug
> when they are separate functions. I would prefer to keep them separate.
> They are also separate in algif_skcipher. It makes it also easier to
> read and understand.
I too would prefer a common function. However we can do this
later if we wish.
> The inflight ctr is incremented only if an asynchronous request has been
> successfully en-queued for processing. If a user forges to call recvmsg
> then the function that increments it won't be even called.
> >From the other hand we don't want to give the option to interrupt the
> wait, because in a case, when we do have request being processed by some
> hardware, and the user kills the process, causing the socket to be
> freed, then we will get an Oops in the callback.
This should be replaced with a sock_hold.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2016-01-19 0:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 19:21 Tadeusz Struk
2016-01-17 15:07 ` Stephan Mueller
2016-01-18 15:22 ` Tadeusz Struk
2016-01-19 0:34 ` Herbert Xu [this message]
2016-01-19 15:18 ` Tadeusz Struk
2016-01-20 20:18 ` Tadeusz Struk
2016-01-21 5:00 ` Herbert Xu
2016-01-27 22:10 Tadeusz Struk
2016-01-27 22:29 ` kbuild test robot
2016-01-27 22:41 ` Tadeusz Struk
2016-01-28 6:26 ` Stephan Mueller
2016-01-28 16:00 ` Tadeusz Struk
2016-01-28 17:09 ` Stephan Mueller
2016-01-28 17:30 ` Tadeusz Struk
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=20160119003428.GA5571@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smueller@chronox.de \
--cc=tadeusz.struk@intel.com \
--cc=tstruk@gmail.com \
/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
all inboxes | Powered by JetHome®