| 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: <20070924091310.c306df35.randy.dunlap@oracle.com> Date: Mon, 24 Sep 2007 09:13:10 -0700 From: Randy Dunlap <randy.dunlap@...cle.com> To: Christoph Hellwig <hch@...radead.org> Cc: David Wilder <dwilder@...ibm.com>, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org Subject: Re: [Patch 1/2] Trace code and documentation (resend) On Mon, 24 Sep 2007 16:41:14 +0100 Christoph Hellwig wrote: > On Mon, Sep 24, 2007 at 08:38:34AM -0700, David Wilder wrote: > > >NACK, don't put code into Documentation/. Put it into kernel as it's > > >actually useful kernel code. > > > > Are you suggesting moving the example code into kernel? Or complaining > > about example code in /Documentation? > > Both. example code should be integrated with the build system so it > gets built. How about if we build the sample files in the Documentation/ tree? with added Kconfig, Makefiles etc. > > And add clone,exec and exit while you're at it. > > > > Hu? A syscall tracer sounds like a nice idea but that is not what I am > > trying to accomplish. I will let Systemtap handle that. > > Systemtap doesn't help anyone as it's not in the tree. I haven't even > asked you to provide a full system call tracing modulem but provide at > least one that's useful for a certain use-case (looking at processes) > instead of almost useless code. --- ~Randy Phaedrus says that Quality is about caring. - 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