linux-kernel - Re: [patch] add /proc/pid/stack to dump task's stack trace

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

Date:	Tue, 11 Nov 2008 15:19:42 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Mikael Pettersson <mikpe@...uu.se>
Cc:	Marcin Slusarz <marcin.slusarz@...il.com>,
	Alexey Dobriyan <adobriyan@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ken Chen <kenchen@...gle.com>, linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [patch] add /proc/pid/stack to dump task's stack trace


* Mikael Pettersson <mikpe@...uu.se> wrote:

> Ingo Molnar writes:
>  > > >  # cat /proc/18579/stack
>  > > >  [<ffffffffffffffff>] 0xffffffffffffffff
>  > > 
>  > > so this file provides view of _kernel_ stack only?
>  > > shouldn't it be named kernel-stack then?
>  > 
>  > it prints the kernel stack right now, but i'd not restrict it to 
>  > the kernel stack conceptually: i think we could eventually expand 
>  > it to print the user-space portion of the stack as well. (in the 
>  > case when user-space is built with frame pointers) We've got code 
>  > for that in the kernel already. It would be an easy one-stop-shop 
>  > for full-range.
> 
> That would be quite fragile given the fact that user-space only has 
> to follow standard ABIs at specific points like calls to standard 
> library functions. In between, anything can, and does, happen.

it's not fragile to robustly walk the userspace stack. The result 
might not always be meaningful of course.

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