diff options
| author | Leonard Crestez <leonard.crestez@nxp.com> | 2018-09-21 18:03:18 +0300 |
|---|---|---|
| committer | Herbert Xu <herbert@gondor.apana.org.au> | 2018-09-28 07:45:37 +0300 |
| commit | d80771c08363ad7fbf0f56f5301e7ca65065c582 (patch) | |
| tree | 8f7a8d92e7d942308902084ad75e7fd13593b186 /drivers/crypto/qat/qat_dh895xcc | |
| parent | add92a817e60e308a419693413a38d9d1e663aff (diff) | |
| download | linux-d80771c08363ad7fbf0f56f5301e7ca65065c582.tar.xz | |
crypto: mxs-dcp - Fix wait logic on chan threads
When compiling with CONFIG_DEBUG_ATOMIC_SLEEP=y the mxs-dcp driver
prints warnings such as:
WARNING: CPU: 0 PID: 120 at kernel/sched/core.c:7736 __might_sleep+0x98/0x9c
do not call blocking ops when !TASK_RUNNING; state=1 set at [<8081978c>] dcp_chan_thread_sha+0x3c/0x2ec
The problem is that blocking ops will manipulate current->state
themselves so it is not allowed to call them between
set_current_state(TASK_INTERRUPTIBLE) and schedule().
Fix this by converting the per-chan mutex to a spinlock (it only
protects tiny list ops anyway) and rearranging the wait logic so that
callbacks are called current->state as TASK_RUNNING. Those callbacks
will indeed call blocking ops themselves so this is required.
Cc: <stable@vger.kernel.org>
Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/crypto/qat/qat_dh895xcc')
0 files changed, 0 insertions, 0 deletions