> > Kernel 2.0.29 with minimal modifications, libc 5.4.23.
>
> libc 5.4.17 here. I compiled the program with debugging, got a core dump,
> and gdb says the program segfaulted trying to access a bad memory location
> during the strncpy (buf, p, 100).
Which is correct, p references a non-readable memory area. What does all
this have to do with an oops in the ext2 code?!
Really, folks, can you try out Bernd's code and see if it oopses on your
particular configuration? Please? :) Drop me a message if you got rid of
the message and I'll forward it to you.
Thanks,
Ionut
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.