linux-kernel - Re: [PATCH 12/17] tracing/probes: Implement 'memory' fetch method for uprobes

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: <87mwk8i3xn.fsf@sejong.aot.lge.com>
Date:	Wed, 11 Dec 2013 10:15:00 +0900
From:	Namhyung Kim <namhyung@...nel.org>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Oleg Nesterov <oleg@...hat.com>,
	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
	Hyeoncheol Lee <cheol.lee@....com>,
	"zhangwei\(Jovi\)" <jovi.zhangwei@...wei.com>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Hemant Kumar <hkshaw@...ux.vnet.ibm.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Namhyung Kim <namhyung.kim@....com>
Subject: Re: [PATCH 12/17] tracing/probes: Implement 'memory' fetch method for uprobes

On Tue, 10 Dec 2013 20:00:37 +0900, Masami Hiramatsu wrote:
> (2013/12/09 15:20), Namhyung Kim wrote:
>> @@ -493,7 +416,7 @@ static int parse_probe_arg(char *arg, const struct fetch_type *t,
>>  			dprm->offset = offset;
>>  			dprm->fetch = t->fetch[FETCH_MTD_memory];
>>  			dprm->fetch_size = get_fetch_size_function(t,
>> -							dprm->fetch, ttbl);
>> +							dprm->fetch, ftbl);
>
> What is this change? I guess it should be included in 11/17...

Argh, right.  It looks like a git rebase artifact, will change.


> The rest of this patch is good for me.

So can I add you ack then? :)

Thank you!
Namhyung
--
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/