From: Andreas Dilger <adilger@clusterfs.com>
If you have ext2_fs.h and ext3_fs.h included at the same time,
we are missing one define used in ext3_should_journal_data() and
ext3_should_order_data() as part of the test_opt() macro (which
defaults to the ext2 definition if both are present).
--- linux-2.4-ext3push/include/linux/ext3_fs.h.=K0006=.orig 2003-03-25 10:59:15.000000000 +0000
+++ linux-2.4-ext3push/include/linux/ext3_fs.h 2003-03-25 10:59:15.000000000 +0000
@@ -349,6 +349,7 @@ struct ext3_inode {
#else
#define EXT2_MOUNT_NOLOAD EXT3_MOUNT_NOLOAD
#define EXT2_MOUNT_ABORT EXT3_MOUNT_ABORT
+#define EXT2_MOUNT_DATA_FLAGS EXT3_MOUNT_DATA_FLAGS
#endif
#define ext3_set_bit ext2_set_bit
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Mar 31 2003 - 22:00:20 EST