diff options
| author | Mathias Krause <minipli@googlemail.com> | 2017-09-08 20:57:11 +0200 |
|---|---|---|
| committer | Herbert Xu <herbert@gondor.apana.org.au> | 2017-10-07 12:10:32 +0800 |
| commit | 350ef88e7e922354f82a931897ad4a4ce6c686ff (patch) | |
| tree | 1a4e182954c15959d059660ba124117c172fe5a3 /drivers/crypto/omap-aes-gcm.c | |
| parent | cf5868c8a22dc2854b96e9569064bb92365549ca (diff) | |
| download | linux-stable-350ef88e7e922354f82a931897ad4a4ce6c686ff.tar.gz linux-stable-350ef88e7e922354f82a931897ad4a4ce6c686ff.tar.bz2 linux-stable-350ef88e7e922354f82a931897ad4a4ce6c686ff.zip | |
padata: ensure padata_do_serial() runs on the correct CPU
If the algorithm we're parallelizing is asynchronous we might change
CPUs between padata_do_parallel() and padata_do_serial(). However, we
don't expect this to happen as we need to enqueue the padata object into
the per-cpu reorder queue we took it from, i.e. the same-cpu's parallel
queue.
Ensure we're not switching CPUs for a given padata object by tracking
the CPU within the padata object. If the serial callback gets called on
the wrong CPU, defer invoking padata_reorder() via a kernel worker on
the CPU we're expected to run on.
Signed-off-by: Mathias Krause <minipli@googlemail.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/crypto/omap-aes-gcm.c')
0 files changed, 0 insertions, 0 deletions