Re: [PATCH] Identify which executable object the userspace addressbelongs to. Store thread group leader id, and use it to lookup theaddress in the process's map. We could have looked up the addresson thread's map, but the thread might not exist by the time we arecalled. The process might not exist either, but if you are readingtrace_pipe, that is unlikely.
From: Christoph Hellwig
Date: Tue Nov 04 2008 - 14:09:36 EST
- Next message: Ian Campbell: "Re: [PATCH] NFS regression in 2.6.26?, "task blocked for more than120 seconds""
- Previous message: H. Peter Anvin: "Re: [PATCH RFC/RFB] x86_64, i386: interrupt dispatch changes"
- In reply to: Török Edwin: "Re: [PATCH] Identify which executable object the userspace addressbelongs to. Store thread group leader id, and use it to lookup the addressin 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 mightnot exist either, but if you are reading trace_pipe, that is unlikely."
- Next in thread: Török Edwin: "Re: [PATCH] Identify which executable object the userspace addressbelongs to. Store thread group leader id, and use it to lookup the addressin 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 mightnot exist either, but if you are reading trace_pipe, that is unlikely."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Next message: Ian Campbell: "Re: [PATCH] NFS regression in 2.6.26?, "task blocked for more than120 seconds""
- Previous message: H. Peter Anvin: "Re: [PATCH RFC/RFB] x86_64, i386: interrupt dispatch changes"
- In reply to: Török Edwin: "Re: [PATCH] Identify which executable object the userspace addressbelongs to. Store thread group leader id, and use it to lookup the addressin 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 mightnot exist either, but if you are reading trace_pipe, that is unlikely."
- Next in thread: Török Edwin: "Re: [PATCH] Identify which executable object the userspace addressbelongs to. Store thread group leader id, and use it to lookup the addressin 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 mightnot exist either, but if you are reading trace_pipe, that is unlikely."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]