> Let me guess, did your copy command avoided overwriting the journal.dat ?
> If not it's not surprizing, that's the only way (with soft raid + ext3)
> I found to get an oops from ext3.
(Sound of head banging against wall... ouch!) Yep, that would do it, I
should have done an --exclude journal.dat...
> I reiterate, the ext3 code must protect the journal from user-level
> process operation, or we are gonna have serious headaches in the user support
> dept. :-(
Maybe at least stick a nice big warning in the docs along the lines of "do
not write to your journal file while mounted with journaling on, you big
dummy!" :) Not that I'd do so deliberately of course, but it might make
people a little more wary later on. The README does recommend setting the
permissions to 400, but that doesn't protect from root of course.
Is there any reason you _would_ want to be able to write to the journal
file from userland while mounted? I'd guess no...
-- brion vibber (brion@pobox.com)
-
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/