linux-kernel - DEBUG_STACKOVERFLOW issue on ARM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGr+u+yxC3nPrsW+EU9qwh0ggjqrg9K=1ftQXfds8unMiDMZsA@mail.gmail.com>
Date:	Wed, 3 Oct 2012 17:18:56 +0530
From:	trisha yad <trisha1march@...il.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>,
	linux-kernel@...r.kernel.org, Ralf Baechle <ralf@...ux-mips.org>
Subject: DEBUG_STACKOVERFLOW issue on ARM

Dear All,
In kernel 3.0.X we find "Check for stackoverflow"
(CONFIG_DEBUG_STACKOVERFLOW) implementation for following
architecture:
frv, mn10300, m32r, tile, x86, mips, powerpc, blackfin except ARM.

Therefore we implemented the similar functionality for ARM in asm_do_IRQ();
We have tested it using a test module.ko that allocate memory on kernel stack.

This test code work fine on single core, but fail to detect stack
overflow in multi-core ARM. While debugging we found that
interrupts were occurring only in CPU0, while the test module was
running in CPU1, since the kernel stack of CPU0 is unaffected
by CPU1 kernel stack, it fails to detect the problem.

However when I upgraded the kernel from 3.0 to 3.4, the stack overflow
detection started working.

I wish to know how can I support this function in 3.0 ?

Regards
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/