linux-kernel - Re: [RFC PATCH] tracing: Add BUG_ON when stack end location is over written

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-prev] [day] [month] [year] [list]

Date:	Mon, 24 Mar 2014 10:39:52 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Aaron Tomlin <atomlin@...hat.com>
Cc:	mingo@...hat.com, dzickus@...hat.com, jgh@...hat.com,
	mguzik@...hat.com, pzijlstr@...hat.com, peterz@...radead.org,
	hpa@...ux.intel.com, riel@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] tracing: Add BUG_ON when stack end location is over
 written

On Mon, 24 Mar 2014 14:03:57 +0000
Aaron Tomlin <atomlin@...hat.com> wrote:

> It is difficult to detect a stack overrun when it
> actually occurs.
> 
> We have observed that this type of corruption is often
> silent and can go unnoticed. Once the corrupted region
> is examined, the outcome is undefined and often
> results in sporadic system crashes.
> 
> When the stack tracing feature is enabled, let's check
> for this condition and take appropriate action.
> 
> Note: init_task doesn't get its stack end location
> set to STACK_END_MAGIC.
> 
> Signed-off-by: Aaron Tomlin <atomlin@...hat.com>
> ---

I added this to my 3.15 queue, and if it survives testing, I'll push it
to my for-next branch.

Thanks,

-- Steve
--
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/