Hi!
On 25/07/2019 15:26, Giovanni Cabiddu wrote:
>> It seems that smp_processor_id() is only used for a best-effort
>> load-balancing, refer to qat_crypto_get_instance_node(). It's not feasible
>> to disable preemption for the duration of the crypto requests. Therefore,
>> just silence the warning. This commit is similar to e7a9b05ca4
>> ("crypto: cavium - Fix smp_processor_id() warnings").
>>
>> Silences the following splat:
>> BUG: using smp_processor_id() in preemptible [00000000] code: cryptomgr_test/2904
>> caller is qat_alg_ablkcipher_setkey+0x300/0x4a0 [intel_qat]
>> CPU: 1 PID: 2904 Comm: cryptomgr_test Tainted: P O 4.14.69 #1
> How did you reproduce this problem?
Isn't just CONFIG_DEBUG_ATOMIC_SLEEP enough in your setup?
--
Best regards,
Alexander Sverdlin.
