Revision 19dbdcb8039cff16669a05136a29180778d16d0a authored by Peter Zijlstra on 18 July 2019, 09:20:09 UTC, committed by Thomas Gleixner on 20 July 2019, 09:27:16 UTC
It's clearly documented that smp function calls cannot be invoked from softirq handling context. Unfortunately nothing enforces that or emits a warning. A single function call can be invoked from softirq context only via smp_call_function_single_async(). The only legit context is task context, so add a warning to that effect. Reported-by: luferry <luferry@163.com> Signed-off-by: Peter Zijlstra <peterz@infradead.org> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Link: https://lkml.kernel.org/r/20190718160601.GP3402@hirez.programming.kicks-ass.net
1 parent 22051d9
| File | Mode | Size |
|---|---|---|
| Kconfig | -rw-r--r-- | 6.1 KB |
| Makefile | -rw-r--r-- | 1.2 KB |
| devres.c | -rw-r--r-- | 7.3 KB |
| extcon-adc-jack.c | -rw-r--r-- | 5.3 KB |
| extcon-arizona.c | -rw-r--r-- | 45.0 KB |
| extcon-axp288.c | -rw-r--r-- | 12.4 KB |
| extcon-fsa9480.c | -rw-r--r-- | 10.1 KB |
| extcon-gpio.c | -rw-r--r-- | 4.3 KB |
| extcon-intel-cht-wc.c | -rw-r--r-- | 12.6 KB |
| extcon-intel-int3496.c | -rw-r--r-- | 4.9 KB |
| extcon-intel-mrfld.c | -rw-r--r-- | 6.8 KB |
| extcon-intel.h | -rw-r--r-- | 384 bytes |
| extcon-max14577.c | -rw-r--r-- | 21.3 KB |
| extcon-max3355.c | -rw-r--r-- | 3.5 KB |
| extcon-max77693.c | -rw-r--r-- | 36.5 KB |
| extcon-max77843.c | -rw-r--r-- | 26.3 KB |
| extcon-max8997.c | -rw-r--r-- | 20.2 KB |
| extcon-palmas.c | -rw-r--r-- | 13.2 KB |
| extcon-ptn5150.c | -rw-r--r-- | 8.3 KB |
| extcon-qcom-spmi-misc.c | -rw-r--r-- | 3.9 KB |
| extcon-rt8973a.c | -rw-r--r-- | 18.8 KB |
| extcon-rt8973a.h | -rw-r--r-- | 7.9 KB |
| extcon-sm5502.c | -rw-r--r-- | 18.9 KB |
| extcon-sm5502.h | -rw-r--r-- | 10.6 KB |
| extcon-usb-gpio.c | -rw-r--r-- | 7.5 KB |
| extcon-usbc-cros-ec.c | -rw-r--r-- | 14.0 KB |
| extcon.c | -rw-r--r-- | 35.5 KB |
| extcon.h | -rw-r--r-- | 2.5 KB |
Computing file changes ...
