Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • autoboot_keyed
  • bootargs
  • stable
  • repro
  • sde
  • set_env_vars
  • cinap_lenrek_sigrid
  • fdtfile
  • env_is_nowhere
  • saveenv
  • distro_bootcmd
  • usb-boot
  • boot.scr
  • hdmi
  • variant-emmc-nvme-boot
  • 2023-10-10
  • 2023-07-04
  • 2023-01-25
  • v3
  • variant-emmc-nvme-boot
  • 2020-06-01
22 results

fs

  • Clone with SSH
  • Clone with HTTPS
  • Forked from Reform / reform-boundary-uboot
    Source project has a limited visibility.
    user avatar
    Yevgeny Popovych authored
    This is the case when reading freshly created filesystem.
    The error message is like the following:
        btrfs_read_superblock: No valid root_backup found!
    
    Since the data from super_roots/root_backups is not actually used -
    decided to rework btrfs_newest_root_backup() into
    btrfs_check_super_roots() that will only check if super_roots
    array is valid and correctly handle empty scenario.
    
    As a result:
    * btrfs_read_superblock() now only checks if super_roots array is valid;
      the case when it is empty is considered OK.
    * removed root_backup pointer from btrfs_info,
      which would be NULL in case of empty super_roots.
    * btrfs_read_superblock() verifies number of devices from the superblock
      itself, not newest root_backup.
    
    Signed-off-by: default avatarYevgeny Popovych <yevgenyp@pointgrab.com>
    Cc: Marek Behun <marek.behun@nic.cz>
    Cc: Sergey Struzh <sergeys@pointgrab.com>
    d146a7b9
    History
    Name Last commit Last update
    ..