| 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
| ||
|
Message-ID: <20070222114326.GA14910@in.ibm.com> Date: Thu, 22 Feb 2007 17:13:26 +0530 From: "S. P. Prasanna" <prasanna@...ibm.com> To: Alan Stern <stern@...land.harvard.edu> Cc: Roland McGrath <roland@...hat.com>, Kernel development list <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] Kwatch: kernel watchpoints using CPU debug registers On Wed, Feb 21, 2007 at 03:35:13PM -0500, Alan Stern wrote: > Going back to something you mentioned earlier... > [...] > On Fri, 9 Feb 2007, Roland McGrath wrote: > There are two things I am uncertain about: vm86 mode and kprobes. I don't > know anything about how either of them works. Judging from the current > code, nothing much should be needed -- debug traps in vm86 mode are > handled by calling handle_vm86_trap(), and kprobes puts itself at the > start of the notify_die() chain so it can handle single-step traps. > Eventually it will be necessary to check with someone who really > understands the issues. Yes, Kprobes needs to get notified first to handle single-step traps. So kwatch getting notified secound should be fine. Thanks Prasanna -- Prasanna S.P. Linux Technology Center India Software Labs, IBM Bangalore Email: prasanna@...ibm.com Ph: 91-80-41776329 - 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