> >>EIP; c0148bf4 <proc_permission+64/f4> <=====
This is *exactly* what I was chasing down last night on the ARM
architecture. In this case, it was caused by:
kernel_thread(xxxx, NULL, 0);
^ - should be
CLONE_FS | CLONE_FILES | CLONE_SIGHAND
This was in the ARM-specific code, so the problem I found is not
exactly the same as yours.
Basically, there is a process running in your kernel which has no
knowledge of a root filesystem. I don't see anything common between
kernel_thread() and your kernel messages to suspect any others
in the generic kernel tree - maybe its a result of a patch you applied?
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/~rmk/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/