diff options
| author | Daniel Jordan <[email protected]> | 2020-04-21 16:34:55 +0000 |
|---|---|---|
| committer | Herbert Xu <[email protected]> | 2020-04-30 05:19:33 +0000 |
| commit | 3c2214b6027ff37945799de717c417212e1a8c54 (patch) | |
| tree | a4fa09b5b3414a84465ab70f7fd525ce914a3bf9 /lib/mpi/longlong.h | |
| parent | hwrng: cctrng - Remove unnecessary FIPS ifdef (diff) | |
| download | kernel-3c2214b6027ff37945799de717c417212e1a8c54.tar.gz kernel-3c2214b6027ff37945799de717c417212e1a8c54.zip | |
padata: add separate cpuhp node for CPUHP_PADATA_DEAD
Removing the pcrypt module triggers this:
general protection fault, probably for non-canonical
address 0xdead000000000122
CPU: 5 PID: 264 Comm: modprobe Not tainted 5.6.0+ #2
Hardware name: QEMU Standard PC
RIP: 0010:__cpuhp_state_remove_instance+0xcc/0x120
Call Trace:
padata_sysfs_release+0x74/0xce
kobject_put+0x81/0xd0
padata_free+0x12/0x20
pcrypt_exit+0x43/0x8ee [pcrypt]
padata instances wrongly use the same hlist node for the online and dead
states, so __padata_free()'s second cpuhp remove call chokes on the node
that the first poisoned.
cpuhp multi-instance callbacks only walk forward in cpuhp_step->list and
the same node is linked in both the online and dead lists, so the list
corruption that results from padata_alloc() adding the node to a second
list without removing it from the first doesn't cause problems as long
as no instances are freed.
Avoid the issue by giving each state its own node.
Fixes: 894c9ef9780c ("padata: validate cpumask without removed CPU during offline")
Signed-off-by: Daniel Jordan <[email protected]>
Cc: Herbert Xu <[email protected]>
Cc: Steffen Klassert <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected] # v5.4+
Signed-off-by: Herbert Xu <[email protected]>
Diffstat (limited to 'lib/mpi/longlong.h')
0 files changed, 0 insertions, 0 deletions
