Revision bb143f814ea488769ca2e79e0b376139cb5f134b authored by Vineet Gupta on 23 February 2016, 06:25:16 UTC, committed by Vineet Gupta on 24 February 2016, 05:37:28 UTC
ARConnect/MCIP Inter-Core-Interrupt module can't send interrupt to local core. So use core intc capability to trigger software interrupt to self, using an unsued IRQ #21. This showed up as csd deadlock with LTP trace_sched on a dual core system. This test acts as scheduler fuzzer, triggering all sorts of schedulting activity. Trouble starts with IPI to self, which doesn't get delivered (effectively lost due to H/w capability), but the msg intended to be sent remain enqueued in per-cpu @ipi_data. All subsequent IPIs to this core from other cores get elided due to the IPI coalescing optimization in ipi_send_msg_one() where a pending msg implies an IPI already sent and assumes other core is yet to ack it. After the elided IPI, other core simply goes into csd_lock_wait() but never comes out as this core never sees the interrupt. Fixes STAR 9001008624 Cc: Peter Zijlstra <peterz@infradead.org> Cc: <stable@vger.kernel.org> [4.2] Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
1 parent 3e5177c
File | Mode | Size |
---|---|---|
Kconfig | -rw-r--r-- | 4.8 KB |
Makefile | -rw-r--r-- | 392 bytes |
TODO | -rw-r--r-- | 772 bytes |
af_ax25.c | -rw-r--r-- | 43.9 KB |
ax25_addr.c | -rw-r--r-- | 6.0 KB |
ax25_dev.c | -rw-r--r-- | 4.7 KB |
ax25_ds_in.c | -rw-r--r-- | 7.1 KB |
ax25_ds_subr.c | -rw-r--r-- | 5.0 KB |
ax25_ds_timer.c | -rw-r--r-- | 5.8 KB |
ax25_iface.c | -rw-r--r-- | 4.9 KB |
ax25_in.c | -rw-r--r-- | 10.5 KB |
ax25_ip.c | -rw-r--r-- | 5.2 KB |
ax25_out.c | -rw-r--r-- | 8.8 KB |
ax25_route.c | -rw-r--r-- | 11.2 KB |
ax25_std_in.c | -rw-r--r-- | 11.1 KB |
ax25_std_subr.c | -rw-r--r-- | 2.3 KB |
ax25_std_timer.c | -rw-r--r-- | 4.2 KB |
ax25_subr.c | -rw-r--r-- | 7.0 KB |
ax25_timer.c | -rw-r--r-- | 5.1 KB |
ax25_uid.c | -rw-r--r-- | 4.8 KB |
sysctl_net_ax25.c | -rw-r--r-- | 4.5 KB |
Computing file changes ...