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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 22 Dec 2012 18:13:29 +0100 From: Oleg Nesterov <oleg@...hat.com> To: Anton Arapov <anton@...hat.com> Cc: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>, LKML <linux-kernel@...r.kernel.org>, Josh Stone <jistone@...hat.com>, Frank Eigler <fche@...hat.com> Subject: Re: [RFC PATCH 5/6] uprobes: add bp_vaddr argument to consumer handler Forgot to ask... On 12/22, Oleg Nesterov wrote: > > On 12/21, Anton Arapov wrote: > > > > struct uprobe_consumer { > > - int (*handler)(struct uprobe_consumer *self, struct pt_regs *regs); > > + int (*handler)(struct uprobe_consumer *self, unsigned long bp_vaddr, struct pt_regs *regs); > > It seems that we can do better... > > Just change regs->ip before calling ->handler(). Josh, Frank, will it work for you? I assume that stap never needs the "real" ->ip after bp, it only needs to know which bp the task hits. And once again, in any case ->ip will be changed after ->handler() is called. Oleg. -- 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