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 for Android: free password hash cracker in your pocket

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

Message-ID: <20120418135815.GA10798@redhat.com>
Date:	Wed, 18 Apr 2012 09:58:15 -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:09:24AM -0400, Steven Rostedt wrote:
 > On Wed, 2012-04-18 at 00:06 -0400, Dave Jones wrote:
 > 
 > > That just prints out..
 > > 
 > > # tracer: function
 > > #
 > > # entries-in-buffer/entries-written: 0/0   #P:4
 > > #
 > > #                              _-----=> irqs-off
 > > #                             / _----=> need-resched
 > > #                            | / _---=> hardirq/softirq
 > > #                            || / _--=> preempt-depth
 > > #                            ||| /     delay
 > > #           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
 > > #              | |       |   ||||       |         |
 > > 
 > >  > I'm also assuming you have CONFIG_STACKTRACE and
 > >  > CONFIG_STACKTRACE_SUPPORT enabled. They should be selected, but configs
 > >  > can always get screwed up.
 > > 
 > > CONFIG_STACKTRACE_SUPPORT=y
 > > CONFIG_STACKTRACE=y
 > > 
 > 
 > OK, function tracing is broken on your box. Could you send me your full
 > config and I'll take a look at it tomorrow. Bed time for me now ;-)

http://fpaste.org/b8PN/raw/

	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/