Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #87817 > unrolled thread

Bug#1107203: unblock: initramfs-tools/0.148.1

Started byBen Hutchings <ben@decadent.org.uk>
First post2025-06-03 00:20 +0200
Last post2025-06-03 00:20 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.debian.kernel


Contents

  Bug#1107203: unblock: initramfs-tools/0.148.1 Ben Hutchings <ben@decadent.org.uk> - 2025-06-03 00:20 +0200

#87817 — Bug#1107203: unblock: initramfs-tools/0.148.1

FromBen Hutchings <ben@decadent.org.uk>
Date2025-06-03 00:20 +0200
SubjectBug#1107203: unblock: initramfs-tools/0.148.1
Message-ID<KTlFD-7zv7-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: initramfs-tools@packages.debian.org, debian-kernel@lists.debian.org
Control: affects -1 + src:initramfs-tools
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package initramfs-tools

[ Reason ]
The unmkinitramfs command is currently a shell script that has to run
multiple processes for each uncompressed cpio archive member in an
initramfs.

This was not too bad when there were usually only a few microcode
blobs in an uncompressed archive, but now that we put compressed
kernel modules in an uncompressed archive, it became very slow indeed.

I fixed this by rewriting it in C.

[ Impact ]
unmkinitramfs is currently very slow.

[ Tests ]
I added an autopkgtest script that tests unmkinitramfs with all
supported sequences of uncompressed and/or compressed cpio archives in
an initramfs image.

unmkinitramfs is also used in autopkgtest scripts for various packages
that integrate with initramfs-tools.

Since unmkinitramfs is supposed to be robust against invalid and
untrusted inputs, I also fuzz-tested it.  In 68 CPU-hours' fuzzing of
the standard build and a build with various sanitizers enabled, I did
not find any issues.

[ Risks ]
As with any rewrite, it's possible that the new implementation doesn't
behave quite like the previous one.  And as with any program written
in C, all kinds of nasty bugs are possible.  However, I think that the
autopkgtest coverage and fuzzing reduce these risks to an acceptable
level.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

[ Other info ]

unblock initramfs-tools/0.148.1

[toc] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web