Hi, Short story: it's again the reiserfs + ext3 issue. I managed to get ext3 and reiserfs into the same tree. Is that safe to use without further patching? Long story: I have a heavily patched kernel (mostly drivers like I²C, dc390 and stuff), among the patches are VM-global-7 by Andrea Arcangeli and ReiserFS 3.5.28. After that, I merged ext3 0.0.5e, there were no conflicts in buffer code or anything (so I assume my last ext3 merge failed for VM-global-7, not for reiserfs). However, the old symbol clashes (buffer_journaled and release_journal) remain. I used perl to rename these symbols to reiserfs_buffer_journaled and reiserfs_release_journal in fs/reiserfs/*.c and include/linux/fs_reiserfs.h, cleaned up the Makefile and *.h rejects (only "bad context" because reiserfs was already there, and prototypes). Now, is there any reason for concern the kernel might cause fs corruption beyond the risk that EITHER reiserfs OR ext3 ONE BY ITSELF infer? The kernel patched like this compiles without relevant warnings and boots up ok, copying from a ro-mounted ext2 to either reiserfs or ext3 does not cause obvious problems, but is there a potential for failure that I can't see at the moment? -- Matthias Andree - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
