linux-kernel - Re: [3.4-rc3] Thread overran stack, or stack corrupted

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

Message-ID: <20120418040702.GC31465@redhat.com>
Date:	Wed, 18 Apr 2012 00:07:02 -0400
From:	Dave Jones <davej@...hat.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [3.4-rc3] Thread overran stack, or stack corrupted

On Wed, Apr 18, 2012 at 12:00:44AM -0400, Steven Rostedt wrote:
 > On Tue, 2012-04-17 at 23:57 -0400, Steven Rostedt wrote:
 > 
 > > Also, have you tested to see if function tracing works?
 > > 
 > > # cd /sys/kernel/debug/tracing
 > > # echo function > current_tracer
 > > # cat trace
 > 
 > Also make sure that the max is zero:
 > 
 > # cat stack_max_size
 > # echo 0 > stack_max_size

Yep, it is zero.

	Dave

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