staging/mkresin/package/base-files, branch master

base-files: simplify restorecon logic

2022-05-02T20:11:05Z

Remove forgotten redundant selinuxenabled call and skip the whole thing in case $IPKG_INSTROOT is set as labels are anyway applied only later on in fakeroot when squashfs is created. Fixes: 6d7272852e ("base-files: add missing $IPKG_INSTROOT to restorecon call") Signed-off-by: Daniel Golle

base-files: add missing $IPKG_INSTROOT to restorecon call

2022-05-02T18:59:58Z

Update to overlooked v2 version of Dominick Grift's patch. Fixes: 5109bd164c ("base-files: address sed in-place without SELinux awareness") Signed-off-by: Daniel Golle

base-files: address sed in-place without SELinux awareness

2022-05-02T17:56:02Z

sed(1) in busybox does not support this functionality: https://git.savannah.gnu.org/cgit/sed.git/tree/sed/execute.c#n598 This causes /etc/group to become mislabeled when a package requests that a uid/gid be added on OpenWrt with SELinux Signed-off-by: Daniel Golle [move restorecon inside lock] Signed-off-by: Dominick Grift

base-files: fix sysupgrade for kernel-out-of-UBI

2022-05-02T11:42:15Z

Commit ecbcc0b59551 bricks devices on which the raw kernel and UBI mtd partitions overlap. This is the case of the ZyXEL NR7101 for example. Its OEM bootloader has no UBI support. OpenWrt splits the stock kernel mtd partition into a raw kernel part used by the bootloader and a UBI part used to store rootfs and rootfs_data. Running mtd erase on the complete partition during sysupgrade erases the UBI part and results in a soft brick. Arguably the best solution would be to fix the partition layouts so that kernel and UBI partitions do not overlap, also including a stock_kernel partition to help reverting to stock firmware. This would have the added benefit of protecting UBI from kernel images that are excessively large. Fixes: ecbcc0b59551 ("base-files: safer sysupgrade.tar for kernel-out-of-UBI") Reported-by: Bjørn Mork Signed-off-by: Rodrigo Balerdi

base-files: minimize critical time in sysupgrade

2022-04-19T15:28:25Z

Attempt to minimize the time during which an interrupted nand sysupgrade can lead to a non-functional device by flushing caches before starting the upgrade procedure. Signed-off-by: Rodrigo Balerdi

base-files: trim unnecessary nand sysupgrade code

2022-04-19T15:28:25Z

Remove unnecessary sync commands during nand sysupgrade. Signed-off-by: Rodrigo Balerdi

base-files: fix issues in nand sysupgrade

2022-04-19T15:28:25Z

Fix issues while retaining configuration during nand sysupgrade: - abort configuration saving if data partition is not found - generate diagnostics if saving fails (eg, because of lack of space) - do not output "sysupgrade successful" in case of errors Signed-off-by: Rodrigo Balerdi

base-files: clean up nand sysupgrade code

2022-04-19T15:28:25Z

Fix some inconsistent quoting in nand sysupgrade code. Signed-off-by: Rodrigo Balerdi

base-files: clean up ubinized sysupgrade code

2022-04-19T15:28:25Z

Remove redundant check from nand ubinized sysupgrade code. This check has already been done in the only caller of the affected function: nand_do_upgrade. Signed-off-by: Rodrigo Balerdi

base-files: clean up nand tar sysupgrade code

2022-04-19T15:28:25Z

Prepares code for ubirename-based safe sysupgrade implementation. Fixes several issues: - the special CI_KERNPART value "none" is ignored if an MTD partition named "none" exists - misleading variable names (such as has_kernel to mean "tar has kernel and it should not be written to an MTD partition but a UBI volume") - inconsistent treatment of zero-length tar member files - inconsistent meaning of "0" and "" variable values - redundant operations (unneeded untaring, repeated untaring, unneeded partition lookups) - inconsistent variable quoting Signed-off-by: Rodrigo Balerdi