[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49109E2B.3030103@gmail.com>
Date: Tue, 04 Nov 2008 21:10:35 +0200
From: Török Edwin <edwintorok@...il.com>
To: Christoph Hellwig <hch@...radead.org>
CC: Ingo Molnar <mingo@...e.hu>, Al Viro <viro@...IV.linux.org.uk>,
srostedt@...hat.com, a.p.zijlstra@...llo.nl, sandmann@...mi.au.dk,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Identify which executable object the userspace address
belongs to. Store thread group leader id, and use it to lookup the address
in the process's map. We could have looked up the address on thread's map,
but the thread might not exist by the time we are called. The process might
not exist either, but if you are reading trace_pipe, that is unlikely.
On 2008-11-04 21:09, Christoph Hellwig wrote:
> On Tue, Nov 04, 2008 at 08:37:11PM +0200, T?r?k Edwin wrote:
>
>> Hmm, this is just for visualizing things in /sys/kernel/debug/, can't I
>> use something simpler than mangle_path, such as a simple while loop like
>> the one below?
>>
>
> Sounds fine to me, although sharing one mangling-scheme for all pathname
> outputs certainly does have benefits of less confusion for the user.
Indeed. I'll do as you suggested: make mangle_path global and document
what it does.
Best regards,
--Edwin
--
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/
Powered by blists - more mailing lists