I guess most stack corruptions touch only a small part of the stack. These kinds of corruptions can only be detected from inside the program.
Anyway, going beyond the program's stack boundaries would fault the program. Checking the threadinfo constantly it'll be (IMHO) mostly useless... On 2/28/07, Chuck Ebbert <[EMAIL PROTECTED]> wrote:
Can we just put a canary in the threadinfo and check it on every task switch? What are the drawbacks? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
-- - Thiago Galesi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
