linux 2.6.16.38 w/ vs2.0.3-rc1

[linux-2.6.git] / include / linux / ext3_fs_i.h

diff --git a/include/linux/ext3_fs_i.h b/include/linux/ext3_fs_i.h
index 7abf901..e71dd98 100644 (file)
--- a/include/linux/ext3_fs_i.h
+++ b/include/linux/ext3_fs_i.h
@@ -19,7 +19,6 @@
 #include <linux/rwsem.h>
 #include <linux/rbtree.h>
 #include <linux/seqlock.h>
-#include <linux/mutex.h>
 
 struct ext3_reserve_window {
        __u32                   _rsv_start;     /* First byte reserved */
@@ -123,16 +122,16 @@ struct ext3_inode_info {
        __u16 i_extra_isize;
 
        /*
-        * truncate_mutex is for serialising ext3_truncate() against
+        * truncate_sem is for serialising ext3_truncate() against
         * ext3_getblock().  In the 2.4 ext2 design, great chunks of inode's
         * data tree are chopped off during truncate. We can't do that in
         * ext3 because whenever we perform intermediate commits during
         * truncate, the inode and all the metadata blocks *must* be in a
         * consistent state which allows truncation of the orphans to restart
         * during recovery.  Hence we must fix the get_block-vs-truncate race
-        * by other means, so we have truncate_mutex.
+        * by other means, so we have truncate_sem.
         */
-       struct mutex truncate_mutex;
+       struct semaphore truncate_sem;
        struct inode vfs_inode;
 };