mirror of https://gitee.com/openkylin/linux.git
x86_64: Don't use softirq safe locks in smp_call_function
It is not fully softirq safe anyways. Can't do a WARN_ON unfortunately because it could trigger in the panic case. Signed-off-by: Andi Kleen <ak@suse.de> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
af3e9a2e33
commit
d9c6d69145
|
@ -386,9 +386,9 @@ int smp_call_function_single (int cpu, void (*func) (void *info), void *info,
|
|||
return 0;
|
||||
}
|
||||
|
||||
spin_lock_bh(&call_lock);
|
||||
spin_lock(&call_lock);
|
||||
__smp_call_function_single(cpu, func, info, nonatomic, wait);
|
||||
spin_unlock_bh(&call_lock);
|
||||
spin_unlock(&call_lock);
|
||||
put_cpu();
|
||||
return 0;
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue