David Smith wrote:
I took a quick look at froggy.c (the kernel module). I'm not sure how
finished
A long, long, way there from--it's still a hacker's sandbox.
you consider it, but in general I'm not sure it is paranoid
enough. For instance, what happens if there is a error in a client
We had a pleasant surprise over the weekend.
The tracehook branch was merged in upstream!
As of 2.6.26-git18, the generic tracehook patches plus the powerpc and
sparc64 arch work are all in. The x86-tracehook branch is in the
hands of the x86 arch maintainers and I expect it will get pushed up
Roland McGrath wrote:
I've read through most of the docs (although my eyes certainly glazed
over when I got to the tracehook stuff).
That stuff is for kernel maintainers, as it says. You don't really need to
know. For that part, just checking for typos is all the help it needs.
What's
David Smith wrote:
I took a quick look at froggy.c (the kernel module). I'm not sure how
finished you consider it, but in general I'm not sure it is paranoid
enough. For instance, what happens if there is a error in a client and
it aborts?
Just looked into that: when a task crashies the
