To make sure that a crashed irq thread does not cause more trouble
when the irq code tries to wake up a gone thread or the device code
calling free_irq and trying to kthread_stop the dead thread, we plug a
pointer to irqaction into task_struct, which is evaluated in
do_exit(). When the thread crashes the do_exit code marks the thread
as DIED in irqaction->flags to prevent further wakeups from the
interrupt handler code.
On thread creation we get a reference to task_struct so it stays
around until the free_irq code releases it again.
The procedure vs. the crashed irq handler thread is slightly racy, but
we do not want to have additional locking in the hard interrupt code
path. The worst things which can happen are a warning that we tried to
wakeup a dead task and a hung kthread_stop in free_irq. I'm not
worried about that at all, as removing a module which had a crashed
interrupt handler is critical anyway.
The main purpose of this is to keep the system alive w/o the affected
Signed-off-by: Thomas Gleixner <firstname.lastname@example.org>
Reviewed-by: Ingo Molnar <email@example.com>
include/linux/interrupt.h | 3 +++
include/linux/sched.h | 1 +
kernel/exit.c | 2 ++
kernel/irq/handle.c | 13 +++++++++++--
kernel/irq/manage.c | 44 +++++++++++++++++++++++++++++++++++++++++---
5 files changed, 58 insertions(+), 5 deletions(-)
@@ -61,6 +61,7 @@
#define IRQF_THREADED 0x00002000
#define IRQF_RUNTHREAD 0x00004000
#define IRQF_WARNED_THREADED 0x00008000
+#define IRQF_THREAD_DIED 0x00010000
typedef irqreturn_t (*irq_handler_t)(int, void *);
@@ -114,6 +115,8 @@ static inline int irq_thread_should_run(
return test_and_clear_bit(IRQF_RUNTHREAD, &action->flags);
+extern void exit_irq_thread(struct ...
Perhaps we could convert parts of the task_struct into a union.
There is quite a lot of things that I'm not sure kernel threads use.
fpu_counter? well, it is only one byte.
Do kernel threads use group_leader?
What about the ptraced items?
group ids/info on kernel threads?
do kernel threads need robust futex info?
This was just a quick look at the task struct. Perhaps we could separate
out kernel only and user space only info and bring the total size down?
Although I'm not sure how much is there that is kernel_thread only :-/
Of course this irqaction will be.