[Bug 1907085] [NEW] Regression in backup-and-restore patch.

[Dimitri John Ledkov]

Public bug reported:

[Impact]

 * A regression was identified in the backup & restore patch on some
architectures, which results in garbage filenames to be created in
/boot/grub.

The issue is reported on linux-ext4 mailing list https://marc.info/?l
=linux-ext4&m=160709231522785&w=2

[Test Case]

 * Execute grub-install --target pc-i386 on i386 machine against a
nonexistent drive. Such that, backup & restore is triggered.

 * Observe that the restored modules names in /boot/grub do not have
garbage file endings.

[Where problems could occur]

 * The generated garbage file endings will remain on disk across future
upgrade and will need to be cleaned up manually. I am pondering if I can
clean them up somehow automatically. However the scope of the affected
machines should be very small and limited to i386.

[Other Info]
 
 * Reported on linux-ext4 mailing list & debugged by / patch provided by colin watson.

** Affects: grub2 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1907085

Title:
  Regression in backup-and-restore patch.

Status in grub2 package in Ubuntu:
  New

Bug description:
  [Impact]

   * A regression was identified in the backup & restore patch on some
  architectures, which results in garbage filenames to be created in
  /boot/grub.

  The issue is reported on linux-ext4 mailing list https://marc.info/?l
  =linux-ext4&m=160709231522785&w=2

  [Test Case]

   * Execute grub-install --target pc-i386 on i386 machine against a
  nonexistent drive. Such that, backup & restore is triggered.

   * Observe that the restored modules names in /boot/grub do not have
  garbage file endings.

  [Where problems could occur]

   * The generated garbage file endings will remain on disk across
  future upgrade and will need to be cleaned up manually. I am pondering
  if I can clean them up somehow automatically. However the scope of the
  affected machines should be very small and limited to i386.

  [Other Info]
   
   * Reported on linux-ext4 mailing list & debugged by / patch provided by colin watson.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1907085/+subscriptions