Opened 6 years ago

Closed 5 years ago

#9289 closed defect (fixed)

runinit.pyx fails to unmount /security/.private

Reported by: dsd Owned by: cscott
Priority: normal Milestone: 8.2.2
Component: initramfs Version: not specified
Keywords: ml8.2.3 Cc: mtd
Blocked By: Blocking:
Deployments affected: Action Needed: review
Verified: no

Description

The unmount /security/.private call in runinit.pyx is not working. Presumably because it is run too late; after a lot of stuff has been wiped out.

This causes all kinds of confusion when the real system tries to shut down, because /proc/mounts says that the mount exists, but the OS can't find it.

This patch makes shut down complete 15 seconds quicker.

Attachments (1)

umount-oatc-private.patch (823 bytes) - added by dsd 6 years ago.

Download all attachments as: .zip

Change History (6)

Changed 6 years ago by dsd

comment:1 Changed 6 years ago by mtd

  • Cc mtd added

comment:2 Changed 5 years ago by martin.langhoff

  • Keywords ml8.2.3 added

comment:3 Changed 5 years ago by martin.langhoff

Daniel,

are you rebuilding the whole initrd from scratch in a Debian chroot? On "the" Debian chroot used for official releases?

To replace runinit.pyx you need the matching environment (python->pyrex->gcc+headers).

comment:4 Changed 5 years ago by martin.langhoff

Ok, was trying to build this for my image, but it clearly needs the full enchilada.

It can only go in -- in an official 8.2.x rel if we can get our hands in the old build environment.

comment:5 Changed 5 years ago by martin.langhoff

  • Milestone changed from Not Triaged to 8.2.2
  • Resolution set to fixed
  • Status changed from new to closed

Built a lenny based chroot (updated docs too!) and rebuilt the initrd correctly.

Note: See TracTickets for help on using tickets.