[PATCH 2/3] clocksource: mtk: Fix race conditions in probe code

2015-02-25 Thread Daniel Lezcano
From: Matthias Brugger We have two race conditions in the probe code which could lead to a null pointer dereference in the interrupt handler. The interrupt handler accesses the clockevent device, which may not yet be registered. First race condition happens when the interrupt handler gets

[PATCH 2/3] clocksource: mtk: Fix race conditions in probe code

2015-02-25 Thread Daniel Lezcano
From: Matthias Brugger We have two race conditions in the probe code which could lead to a null pointer dereference in the interrupt handler. The interrupt handler accesses the clockevent device, which may not yet be registered. First race condition happens when the interrupt handler gets

[PATCH 2/3] clocksource: mtk: Fix race conditions in probe code

2015-02-25 Thread Daniel Lezcano
From: Matthias Brugger matthias@gmail.com We have two race conditions in the probe code which could lead to a null pointer dereference in the interrupt handler. The interrupt handler accesses the clockevent device, which may not yet be registered. First race condition happens when the

[PATCH 2/3] clocksource: mtk: Fix race conditions in probe code

2015-02-25 Thread Daniel Lezcano
From: Matthias Brugger matthias@gmail.com We have two race conditions in the probe code which could lead to a null pointer dereference in the interrupt handler. The interrupt handler accesses the clockevent device, which may not yet be registered. First race condition happens when the