linux-kernel - Re: [QUESTION] Can uprobe_event support @ADDR, $retval, offs(FETCHARG)?

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: <20120926044238.GC27339@linux.vnet.ibm.com>
Date:	Wed, 26 Sep 2012 10:12:38 +0530
From:	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
To:	Hyeoncheol Lee <hyc.lee@...il.com>
Cc:	masami.hiramatsu.pt@...achi.com, linux-kernel@...r.kernel.org
Subject: Re: [QUESTION] Can uprobe_event support @ADDR, $retval,
 offs(FETCHARG)?

Hi Hyeoncheol,

> uprobe_event only supports %REG arguments. I think that memory fetch,
> return value fetch, memory dereference functions in
> kernel/trace/trace_probe.c are good for uprobe_event.

Yes, these will be good to have and is listed as todo.

> So with a little
> modification of parse_probe_arg(), uprobe_event can support @ADDR,
> $retval, offs(FETCHARGS) except @SYM, $stack, $stackN. Is it right?

For some of these like the @sym, trace_uprobe.c may not be the right
place because the kernel will not be able to decode user space symbols. 

$retval needs uretprobes support

-- 
Thanks and Regards
Srikar

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