Re: [PATCH net-next v2] ibmvnic: Don't handle RX interrupts when not up.

2018-01-11 Thread David Miller
From: Nathan Fontenot Date: Wed, 10 Jan 2018 10:40:09 -0600 > Initiating a kdump via the command line can cause a pending interrupt > to be handled by the ibmvnic driver when initializing the sub-CRQ > irqs during driver initialization. ... > At this point the driver is not prepared to handle tr

Re: [PATCH net-next v2] ibmvnic: Don't handle RX interrupts when not up.

2018-01-10 Thread Thomas Falcon
On 01/10/2018 10:40 AM, Nathan Fontenot wrote: > Initiating a kdump via the command line can cause a pending interrupt > to be handled by the ibmvnic driver when initializing the sub-CRQ > irqs during driver initialization. > > NIP [d0ca34f0] ibmvnic_interrupt_rx+0x40/0xd0 [ibmvnic] > LR [c

[PATCH net-next v2] ibmvnic: Don't handle RX interrupts when not up.

2018-01-10 Thread Nathan Fontenot
Initiating a kdump via the command line can cause a pending interrupt to be handled by the ibmvnic driver when initializing the sub-CRQ irqs during driver initialization. NIP [d0ca34f0] ibmvnic_interrupt_rx+0x40/0xd0 [ibmvnic] LR [c8132ef0] __handle_irq_event_percpu+0xa0/0x2f0 Call