11 Jul, 2016

1 commit


24 Sep, 2015

1 commit

  • Configuration option EXT4_USE_FOR_EXT2 has no effect on ext3 support.
    Support for ext3 is always included now.

    Signed-off-by: Jean Delvare
    Fixes: c290ea01ab ("fs: Remove ext3 filesystem driver")
    Cc: Jan Kara
    Cc: Theodore Ts'o
    Cc: Andreas Dilger
    Signed-off-by: Jan Kara

    Jean Delvare
     

24 Jul, 2015

2 commits

  • Now that ext4 driver must be used to access ext3 filesystems, improve
    the Kconfig help text to better explain that using ext4 driver to access
    the filesystem is fully compatible with the old ext3 driver.

    Acked-by: Theodore Ts'o
    Signed-off-by: Jan Kara

    Jan Kara
     
  • The functionality of ext3 is fully supported by ext4 driver. Major
    distributions (SUSE, RedHat) already use ext4 driver to handle ext3
    filesystems for quite some time. There is some ugliness in mm resulting
    from jbd cleaning buffers in a dirty page without cleaning page dirty
    bit and also support for buffer bouncing in the block layer when stable
    pages are required is there only because of jbd. So let's remove the
    ext3 driver. This saves us some 28k lines of duplicated code.

    Acked-by: Theodore Ts'o
    Signed-off-by: Jan Kara

    Jan Kara
     

01 Jun, 2015

1 commit


02 May, 2015

1 commit


11 Apr, 2015

1 commit


22 Apr, 2013

1 commit


07 Jan, 2013

1 commit

  • Commit "ext4: Remove CONFIG_EXT4_FS_XATTR" removed the configuration
    dependencies for ext4 xattrs from the ext4 ACLs and security labels
    configuration options, but did not replace them with a dependency on
    ext4 itself. Add back the dependency on ext4 so the options only show
    up if ext4 is enabled.

    Signed-off-by: Valerie Aurora
    Signed-off-by: "Theodore Ts'o"
    Reviewed-by: Tao Ma

    Valerie Aurora
     

11 Dec, 2012

1 commit

  • Ted has sent out a RFC about removing this feature. Eric and Jan
    confirmed that both RedHat and SUSE enable this feature in all their
    product. David also said that "As far as I know, it's enabled in all
    Android kernels that use ext4." So it seems OK for us.

    And what's more, as inline data depends its implementation on xattr,
    and to be frank, I don't run any test again inline data enabled while
    xattr disabled. So I think we should add inline data and remove this
    config option in the same release.

    [ The savings if you disable CONFIG_EXT4_FS_XATTR is only 27k, which
    isn't much in the grand scheme of things. Since no one seems to be
    testing this configuration except for some automated compile farms, on
    balance we are better removing this config option, and so that it is
    effectively always enabled. -- tytso ]

    Cc: David Brown
    Cc: Eric Sandeen
    Reviewed-by: Jan Kara
    Signed-off-by: Tao Ma
    Signed-off-by: "Theodore Ts'o"

    Tao Ma
     

30 Apr, 2012

1 commit


21 Dec, 2009

1 commit


18 Dec, 2009

1 commit

  • This reverts commit e4c570c4cb7a95dbfafa3d016d2739bf3fdfe319, as
    requested by Alexey:

    "I think I gave a good enough arguments to not merge it.
    To iterate:
    * patch makes impossible to start using ext3 on EXT3_FS=n kernels
    without reboot.
    * this is done only for one pointer on task_struct"

    None of config options which define task_struct are tristate directly
    or effectively."

    Requested-by: Alexey Dobriyan
    Acked-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Linus Torvalds
     

16 Dec, 2009

1 commit

  • journal_info in task_struct is used in journaling file system only. So
    introduce CONFIG_FS_JOURNAL_INFO and make it conditional.

    Signed-off-by: Hiroshi Shimamoto
    Cc: Chris Mason
    Cc: "Theodore Ts'o"
    Cc: Steven Whitehouse
    Cc: KONISHI Ryusuke
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Hiroshi Shimamoto
     

10 Dec, 2009

1 commit


08 Dec, 2009

1 commit

  • Add a new config option, CONFIG_EXT4_USE_FOR_EXT23 which if enabled,
    will cause ext4 to be used for either ext2 or ext3 file system mounts
    when ext2 or ext3 is not enabled in the configuration.

    This allows minimalist kernel fanatics to drop to file system drivers
    from their compiled kernel with out losing functionality.

    Signed-off-by: "Theodore Ts'o"

    Theodore Ts'o
     

01 Oct, 2009

1 commit


19 Sep, 2009

1 commit


28 Jul, 2009

1 commit


30 Mar, 2009

1 commit


21 Oct, 2008

1 commit