1. 27 Dec, 2016 1 commit
  2. 21 Nov, 2016 2 commits
  3. 24 Oct, 2016 3 commits
  4. 23 Sep, 2016 27 commits
  5. 05 Aug, 2016 1 commit
    • ext4: Refuse to mount filesystems with 64bit feature set · 6f94ab66
      Tom Rini authored
      With e2fsprogs after 1.43 the 64bit and metadata_csum features are
      enabled by default.  The metadata_csum feature changes how
      ext4_group_desc->bg_checksum is calculated, which would break write
      support.  The 64bit feature however introduces changes such that it
      cannot be read by implementations that do not support it.  Since we do
      not support this, we must not mount it.
      
      Cc: Stephen Warren <swarren@nvidia.com>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Lukasz Majewski <l.majewski@samsung.com>
      Cc: Stefan Roese <sr@denx.de>
      Reported-by: 's avatarAndrew Bradford <andrew.bradford@kodakalaris.com>
      Signed-off-by: 's avatarTom Rini <trini@konsulko.com>
  6. 02 May, 2016 1 commit
  7. 14 Mar, 2016 2 commits
  8. 14 Jan, 2016 2 commits
  9. 23 Nov, 2015 1 commit
    • fs: ext4: Prevent infinite loop in ext4fs_iterate_dir · 54d68e93
      Thomas Fitzsimmons authored
      If the ext3 journal gets out of sync with what is written on disk, for
      example because of an unexpected power cut, ext4fs_read_file can
      return an all-zero directory entry.  In that case, ext4fs_iterate_dir
      would infinite loop.
      
      This patch detects when a directory entry's direntlen member is 0 and
      returns a failure status, which breaks out of the infinite loop.  As a
      result, U-Boot will not find files that may subsequently be recovered
      when the journal is replayed.
      
      This is better behaviour than hanging in an infinite loop, but as a
      further improvement maybe U-Boot could interpret the ext3 journal and
      actually find the unsynced entries.
      Signed-off-by: 's avatarThomas Fitzsimmons <fitzsim@cisco.com>
      Reviewed-by: 's avatarStefan Roese <sr@denx.de>