eMMC regression in Linux master and stable breaks boot-emmc updates

[jluebbe]

A change in the MMC stack in the Linux kernel introduced a regression when changing the active eMMC boot partition after an update. In RAUC, this affects bootloader updates using the boot-emmc slot type. Sometimes a check in RAUC detects the problem and aborts the installation with a message similar to Installation error: Failed updating slot bootloader.0: Toggling the boot partition failed!. If RAUC doesn't detect the issue, it can happen that the old partition is still active after the update completes.

The problematic change was identified here. A fix is available here and has been back-ported to the affected stable branches.

The following versions are affected: v6.8…v6.8.2, v6.7.3…v6.7.11, v6.6.15…v6.6.23, v6.1.76…v6.1.83, v5.15.149…v5.15.153, v5.10.210…v5.10.214, v5.4.269…v5.4.273

The relevant commits are...

• master: introduced with torvalds/linux@4d0c8d0 in v6.8-rc
  • fixed with torvalds/linux@0cdfe5b in v6.9-rc2
• stable-6.8: introduced during development phase
  • fixed with gregkh/linux@d7b24b0 in v6.8.3
• stable-6.7: backported as gregkh/linux@eed9119 in v6.7.3
  • fixed with gregkh/linux@59169ee in v6.7.12
• stable-6.6: backported as gregkh/linux@1653a81 in v6.6.15
  • fixed with gregkh/linux@35ee852 in v6.6.24
• stable-6.1: backported as gregkh/linux@c4edcd1 in v6.1.76
  • fixed with gregkh/linux@547f4af in v6.1.84
• stable-5.15: backported as gregkh/linux@50b8b7a in v5.15.149
  • fixed with gregkh/linux@0ecd568 in v5.15.154
• stable-5.10: backported as gregkh/linux@59020bf in v5.10.210
  • fixed with gregkh/linux@bce3a98 in v5.10.215
• stable-5.4: backported as gregkh/linux@f49f9e8 in v5.4.269
  • fixed with gregkh/linux@fd20d84 in v5.4.274

[a3f]

The fix is now mainline:

• master: Fixed with torvalds/linux@0cdfe5b in v6.9-rc2

and should soon make it into stable releases. I'll update this comment when that happens.

[jluebbe]

Fixes have now landed in some stable releases: v6.8.3, v6.7.12, v6.6.24 and v6.1.84. See the updated post above for the exact commits.

[a3f]

stable-5.15: fixed with gregkh/linux@0ecd568 in v5.15.154

[a3f]

• stable-5.10: fixed with gregkh/linux@bce3a98 in v5.10.215
• stable-5.4: fixed with gregkh/linux@fd20d84 in v5.4.274