Nothing in arch/i386/kernel/traps.c uses a task gate, they are all
interrupt, trap, system or call gates. I guarantee that kdb on ix86
and ia64 uses the same kernel stack as the failing task, the starting
point for the kdb backtrace is itself and it does not follow segment
switches.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/