|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v3 3/4] xen/drivers/char/cadence-uart: fix IRQ registration failure propagation
On 4/22/26 12:33, Oleksii Moisieiev wrote: Hello Oleksii In cuart_init_postirq(), two code paths could reach the interrupt-enable write to IER without a handler being registered: - When no valid IRQ number was provided (uart->irq <= 0), the original positive-condition guard (if uart->irq > 0) skipped the irqaction setup but still fell through to the IER write, enabling the receive data interrupt with no handler installed. - When setup_irq() returned an error, only an error message was printed and execution continued to the IER write, arming the receive hardware interrupt line with no handler to service it. On platforms where the GIC receives this asserted line, the result is either repeated spurious-interrupt warnings or an unhandled interrupt fault. Restructure cuart_init_postirq() to use early returns in both error paths. Signed-off-by: Oleksii Moisieiev <oleksii_moisieiev@xxxxxxxx> --- Changes in v3: - clear pending error interrupts before setup_irq call for cadence uart - change uart->irq <= 0 to uart->irq == 0 since irq is unsigned Reviewed-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@xxxxxxxx> with NIT (could probably be fixed on commit) ...
... the format specifier should be %u instead of %d since the value is unsigned.
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |