Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=cbcae39fa1cc16c0fb199223f5ec1aea5f4c7b2d
Commit:     cbcae39fa1cc16c0fb199223f5ec1aea5f4c7b2d
Parent:     cca97de1184f6000d22b4106d47687b31cca1fa3
Author:     Evgeniy Dushistov <[EMAIL PROTECTED]>
AuthorDate: Mon Feb 12 00:54:30 2007 -0800
Committer:  Linus Torvalds <[EMAIL PROTECTED]>
CommitDate: Mon Feb 12 09:48:40 2007 -0800

    [PATCH] ufs2 write: mount as rw
    
    These series of patches add UFS2 write-support.  UFS2 - is default file 
system
    for recent versions of FreeBSD.
    
    The main differences from UFS1 from write support point of view
    are:
    1)Not all inodes are allocated during formatation of disk.
    2)All meta-data(pointer to data blocks) are 64bit(in UFS1 they
    are 32bit).
    
    So patch series consist of
    1)make possible mount UFS2 in read-write mode
    2)code to write ufs2 inodes and code to initialize inodes chunks.
    3)work with 64bit meta-data
    
    I made simple testing like create/deleting/writing/reading/truncating, also 
I
    ran fsx-linux and untar and build kernel on UFS1 and UFS2, after that 
FreeBSD
    fsck do not find any errors in fs.
    
    This patch makes possible to mount ufs2 "rw", and updates UFS2 
documentation:
    remove note about bug(it fixed by reallocate blocks on the fly patch) and 
add
    me in the list of people who want receive bug reports.
    
    Signed-off-by: Evgeniy Dushistov <[EMAIL PROTECTED]>
    Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
    Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
---
 Documentation/filesystems/ufs.txt |    9 ++++-----
 fs/ufs/super.c                    |    9 ++++-----
 2 files changed, 8 insertions(+), 10 deletions(-)

diff --git a/Documentation/filesystems/ufs.txt 
b/Documentation/filesystems/ufs.txt
index 2b5a56a..7a602ad 100644
--- a/Documentation/filesystems/ufs.txt
+++ b/Documentation/filesystems/ufs.txt
@@ -21,7 +21,7 @@ ufstype=type_of_ufs
                supported as read-write
 
        ufs2    used in FreeBSD 5.x
-               supported as read-only
+               supported as read-write
 
        5xbsd   synonym for ufs2
 
@@ -50,12 +50,11 @@ ufstype=type_of_ufs
 POSSIBLE PROBLEMS
 =================
 
-There is still bug in reallocation of fragment, in file fs/ufs/balloc.c, 
-line 364. But it seems working on current buffer cache configuration.
+See next section, if you have any.
 
 
 BUG REPORTS
 ===========
 
-Any ufs bug report you can send to [EMAIL PROTECTED] (do not send 
-partition tables bug reports.)
+Any ufs bug report you can send to [EMAIL PROTECTED] or
+to [EMAIL PROTECTED] (do not send partition tables bug reports).
diff --git a/fs/ufs/super.c b/fs/ufs/super.c
index 209be95..1427e44 100644
--- a/fs/ufs/super.c
+++ b/fs/ufs/super.c
@@ -61,6 +61,8 @@
  * UFS2 (of FreeBSD 5.x) support added by
  * Niraj Kumar <[EMAIL PROTECTED]>, Jan 2004
  *
+ * UFS2 write support added by
+ * Evgeniy Dushistov <[EMAIL PROTECTED]>, 2007
  */
 
 
@@ -674,10 +676,6 @@ static int ufs_fill_super(struct super_block *sb, void 
*data, int silent)
                uspi->s_sbsize = super_block_size = 1536;
                uspi->s_sbbase =  0;
                flags |= UFS_TYPE_UFS2 | UFS_DE_44BSD | UFS_UID_44BSD | 
UFS_ST_44BSD | UFS_CG_44BSD;
-               if (!(sb->s_flags & MS_RDONLY)) {
-                       printk(KERN_INFO "ufstype=ufs2 is supported 
read-only\n");
-                       sb->s_flags |= MS_RDONLY;
-               }
                break;
                
        case UFS_MOUNT_UFSTYPE_SUN:
@@ -1156,7 +1154,8 @@ static int ufs_remount (struct super_block *sb, int 
*mount_flags, char *data)
 #else
                if (ufstype != UFS_MOUNT_UFSTYPE_SUN && 
                    ufstype != UFS_MOUNT_UFSTYPE_44BSD &&
-                   ufstype != UFS_MOUNT_UFSTYPE_SUNx86) {
+                   ufstype != UFS_MOUNT_UFSTYPE_SUNx86 &&
+                   ufstype != UFS_MOUNT_UFSTYPE_UFS2) {
                        printk("this ufstype is read-only supported\n");
                        return -EINVAL;
                }
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to