The introduction of call_softirq switching to the interrupt stack several releases earlier resulted in a problem with the code in show_trace, which assumes that it can pick the previous stack pointer from the end of the interrupt stack. From: Jan Beulich <[email protected]> (actual patch attached)
Attachment:
linux-2.6.14-x86_64-call-softirq.patch
Description: Binary data
- Prev by Date: Re: negative timeout can be set up by setsockopt system call
- Next by Date: Re: [PATCH][MCAST]Clear MAF_GSQUERY flag when process MLDv1 general query messages.
- Previous by thread: [PATCH][MCAST]Clear MAF_GSQUERY flag when process MLDv1 general query messages.
- Next by thread: [PATCH] Shut up per_cpu_ptr() on UP
- Index(es):
 |