| 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: <20070331130601.GA18947@infradead.org> Date: Sat, 31 Mar 2007 14:06:01 +0100 From: Christoph Hellwig <hch@...radead.org> To: "Stone, Joshua I" <joshua.i.stone@...el.com> Cc: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@...el.com>, Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>, Ananth N Mavinakayanahalli <ananth@...ibm.com>, Prasanna S Panchamukhi <prasanna@...ibm.com>, linux-kernel <linux-kernel@...r.kernel.org>, SystemTAP <systemtap@...rces.redhat.com>, Satoshi Oshima <soshima@...hat.com>, Hideo Aoki <haoki@...hat.com>, Yumiko Sugita <yumiko.sugita.yf@...achi.com>, "Frank Ch. Eigler" <fche@...hat.com>, hch@...radead.org Subject: Re: [RFC][Patch 1/4] kprobe fast unregistration On Fri, Mar 23, 2007 at 11:12:22AM -0700, Stone, Joshua I wrote: > The ability to disable/reenable kprobes would be an interesting > enhancement. However, unregister_disabled_kprobes() shouldn't have a > global effect, because there might be a concurrent kprobes user that > disabled a probe with the intention of reenabling it later. enabling/disabling probes sounds like a wonderful additional feature. I don't think we should expose it as a kernel interface, but rather through debugfs so I can temporarily disable and then reenable probes from the shell easily. - 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