null pointer dereference error in mtk_timer.c

From: ëìë
Date: Mon Feb 16 2015 - 03:20:30 EST

Hello. My name is Yongbae Park.

I would like to report a possible null pointer dereference error at
mtk_timer_interrupt() in drivers/clocksource/mtk_timer.c (version:
3.19-rc5). The null pointer dereference error occurs if the interrupt
handler mtk_timer_interrupt() accesses evt->dev.event_handler (line
146) when evt->dev.event_handler is null and not defined by

mtk_timer_init() first registers mtk_timer_interrupt() as the
interrupt handler at line 227, and then defines the clockevent handler
at line 246. As a consequence, the interrupt handler can be executed
before the clockevent handler definition when an interrupt occurs
between line 227 and line 246. The detail error scenario is the

183: static void __init mtk_timer_init(struct device_node *node) {
227: if (request_irq(evt->dev.irq, mtk_timer_interrupt,
228: IRQF_TIMER | IRQF_IRQPOLL, "mtk_timer", evt)) {
------ An interrupt is fired and the interrupt handler is called -------
140: static irqreturn_t mtk_timer_interrupt(int irq, void *dev_id)
141: {
142: struct mtk_clock_event_device *evt = dev_id;
144: /* Acknowledge timer0 irq */
145: writel(GPT_IRQ_ACK(GPT_CLK_EVT), evt->gpt_base + GPT_IRQ_ACK_REG);
146: evt->dev.event_handler(&evt->dev); //evt->dev.event_handler
is not defined
148: return IRQ_HANDLED;
149: }
------ The execution of the interrupt handler is finished ------
246: clockevents_config_and_register(&evt->dev, rate, 0x3,
247: 0xffffffff);

To resolve the problem, I think that the interrupt handler should be
registered after the clock handler registration.

For your information, I give you the references to similar issues from
the previous bug reports:

Thank you.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at