1. 08 9月, 2020 4 次提交
    • Q
      fs: btrfs: Crossport rbtree-utils from btrfs-progs · bc621e54
      Qu Wenruo 提交于
      This is needed for incoming extent-cache infrastructure.
      Signed-off-by: NQu Wenruo <wqu@suse.com>
      Reviewed-by: NMarek Behún <marek.behun@nic.cz>
      bc621e54
    • Q
      fs: btrfs: Crossport btrfs_read_dev_super() from btrfs-progs · 4aebb994
      Qu Wenruo 提交于
      This patch uses generic code from btrfs-progs to read one super block
      from block device.
      
      To support the btrfs-progs coding style, the following is also
      crossported:
      - BTRFS_SETGET_FUNC for btrfs_super_block
      - btrfs_check_super() function
      - Move btrfs_read_superblock() to disk-io.[ch]
        Since super.c only contains pretty small amount of code, and
        the extra check will be covered in later root read patches.
      
      Differences between this implementation and btrfs-progs:
      - No sbflags/sb_bytenr support
        Since we only need to read the primary super block (like kernel),
        sbflags/sb_bytenr used by super block recovery is not needed.
      
      This also changes the following behavior of U-Boot btrfs:
      - Only reads the primary super block
        The old implementation reads all 3 super blocks, and also one
        non-existing backup.
        This is not correct, especially if there is another filesystem created
        on the device but old superblocks are not rewritten.
      
        Just like kernel, we only check the primary super block.
      Signed-off-by: NQu Wenruo <wqu@suse.com>
      Reviewed-by: NMarek Behún <marek.behun@nic.cz>
      [trini: Change error to be a define in compat.h]
      Signed-off-by: NTom Rini <trini@konsulko.com>
      4aebb994
    • Q
      fs: btrfs: Add more checksum algorithms · 565a4147
      Qu Wenruo 提交于
      This mostly crossports crypto/hash.[ch] from btrfs-progs.
      
      The differences are:
      - No blake2 support
        No blake2 related library in U-Boot yet.
      
      - Use uboot xxhash/sha256 directly
        No need to implement the code as U-Boot has already provided the
        interface.
      
      This adds the support for the following csums:
      - SHA256
      - XXHASH
      Signed-off-by: NQu Wenruo <wqu@suse.com>
      Reviewed-by: NMarek Behún <marek.behun@nic.cz>
      565a4147
    • Q
      fs: btrfs: Sync btrfs_btree.h from kernel · 3b4b40c0
      Qu Wenruo 提交于
      This version includes all needed on-disk format from kernel.
      
      Only need to modify the include headers for U-Boot, everything else is
      untouched.
      
      Also, since U-Boot btrfs is using a different endian convert timing (at
      tree block read time), it needs some forced type conversion before
      proper crossport.
      Signed-off-by: NQu Wenruo <wqu@suse.com>
      Reviewed-by: NMarek Behún <marek.behun@nic.cz>
      3b4b40c0
  2. 07 9月, 2020 1 次提交
  3. 25 8月, 2020 5 次提交
  4. 08 8月, 2020 4 次提交
  5. 05 8月, 2020 1 次提交
    • J
      fs/fat/fat.c: Do not perform zero block reads if there are no blocks left · 5b3ddb17
      Jason Wessel 提交于
      While using u-boot with qemu's virtio driver I stumbled across a
      problem reading files less than sector size.  On the real hardware the
      block reader seems ok with reading zero blocks, and while we could fix
      the virtio host side of qemu to deal with a zero block read instead of
      crashing, the u-boot fat driver should not be doing zero block reads
      in the first place.  If you ask hardware to read zero blocks you are
      just going to get zero data.  There may also be other hardware that
      responds similarly to the virtio interface so this is worth fixing.
      
      Without the patch I get the following and have to restart qemu because
      it dies.
      ---------------------------------
      => fatls virtio 0:1
             30   cmdline.txt
      => fatload virtio 0:1 ${loadaddr} cmdline.txt
      qemu-system-aarch64: virtio: zero sized buffers are not allowed
      ---------------------------------
      
      With the patch I get the expected results.
      ---------------------------------
      => fatls virtio 0:1
             30   cmdline.txt
      => fatload virtio 0:1 ${loadaddr} cmdline.txt
      30 bytes read in 11 ms (2 KiB/s)
      => md.b ${loadaddr} 0x1E
      40080000: 64 77 63 5f 6f 74 67 2e 6c 70 6d 5f 65 6e 61 62    dwc_otg.lpm_enab
      40080010: 6c 65 3d 30 20 72 6f 6f 74 77 61 69 74 0a          le=0 rootwait.
      
      ---------------------------------
      Signed-off-by: NJason Wessel <jason.wessel@windriver.com>
      Signed-off-by: NJason Wessel <jason.wessel@windriver.com>
      Reviewed-by: NTom Rini <trini@konsulko.com>
      5b3ddb17
  6. 17 7月, 2020 1 次提交
  7. 12 7月, 2020 1 次提交
  8. 08 7月, 2020 2 次提交
  9. 07 7月, 2020 1 次提交
    • C
      fs: fat: fix fat iteration · 1788a969
      Christian Gmeiner 提交于
      According to the FAT specification it is valid to have files with an
      attribute value of 0x0. This fixes a regression where different U-Boot
      versions are showing different amount of files on the same storage
      device. With this change U-Boot shows the same number of files and folders
      as Linux and Windows.
      
      Fixes: 39606d46 ("fs: fat: handle deleted directory entries correctly")
      Signed-off-by: NChristian Gmeiner <christian.gmeiner@gmail.com>
      1788a969
  10. 27 5月, 2020 13 次提交
  11. 19 5月, 2020 7 次提交