Re: [PATCH 0/13] maps: pagemap, kpagemap, and related cleanups

[Nick Piggin <nickpiggin@yahoo.com.au>]

Christoph Hellwig wrote:
> On Fri, Apr 13, 2007 at 05:05:47PM +1000, Nick Piggin wrote:
> 
>>Ah, OK. Anyway, with kprobes/systemtap they can do whatever they like
>>and none of us need to care in the slightest ;)
> 
> 
> Umm, folks.  systemtap basically means people compile kernel modules
> from an odd scripting language with embedded C snipplets into kernel
> modules.  The kernel modules don't use normal exported APIs but use
> kallsysms and dwarf info to poke into every possible private bit.
> 
> Saying you don't care the slightest whether oracle will load huge
> amounts of code into the kernel that depends on intimate implementation
> details, and that you don't even have source to to debug it is not what
> I'd call "none of us need to care in the slightest", at least for those
> of you working for distributions that may actually have to debug this
> shit in the end.

Yeah good point ;) I just meant the wider "we".

With all the problems kprobes has, something like poking deep into
kernel internals seems like a good thing to use it for instead of
hardcoding that stuff into the kernel. If not, then why did we even
merge it in the first place?

We could distribute some systemtap scripts, and even distribute some
basic useful ones like this sort of page info in the kernel source
tree.


> While we're at it, what happened to the idea of tainting the kernel
> as soon as krpobes are placed in the kernel to at least make people
> aware of it?

Seems like a very good idea.


-- 
SUSE Labs, Novell Inc.