My new and improved rpctrace is generating kernel panics when run on ext2fs. This happens when rpctrace calls gsync_wait, with ext2fs as the 'task' argument.
Could you guys look at gnumach's kern/gsync.c, at line 212? It looks to me like that code tacitly assumes that the 'addr' it's accessing is in the memory space of the task calling the RPC, instead of the task passed in as the first argument.
Even if I'm right about the nature of this bug, I don't understand gnumach well enough to know how a task should access another task's memory.