linux-kernel - Re: [PATCH 2/2] tracing: identify which executable object the userspace address belongs to

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: <20081127124851.GC23480@redhat.com>
Date:	Thu, 27 Nov 2008 07:48:51 -0500
From:	"Frank Ch. Eigler" <fche@...hat.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Török Edwin <edwintorok@...il.com>,
	mingo@...e.hu, srostedt@...hat.com, sandmann@...mi.au.dk,
	linux-kernel@...r.kernel.org, viro@...IV.linux.org.uk
Subject: Re: [PATCH 2/2] tracing: identify which executable object the userspace address belongs to

Hi -

On Thu, Nov 27, 2008 at 11:41:45AM +0100, Peter Zijlstra wrote:
> > > Impact: modify+improve the userstacktrace tracing visualization feature
> > > [...]
> > > You'll see stack entries like:
> > >    /lib/libpthread-2.7.so[+0xd370]
> > > [...]
> > 
> > Can you suggest an actual distribution & architecture where this
> > facility may be tested/used?  It appears to require frame-pointer
> > stuff that AFAIK is not generally turned on for user-space.
> 
> gentoo, just rebuild world with frame pointers ;-)

Well, that only goes so far.  If this feature turns out unable to work
without distributors recompiling all their stuff on, for example, x86-64,
then expectations need to be reset.


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