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


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

Bug#1034648: postinst runs linux-update-symlinks before initrd exists

Started byJoey Hess <id@joeyh.name>
First post2023-04-20 22:20 +0200
Last post2023-04-25 20:30 +0200
Articles 5 — 3 participants

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


Contents

  Bug#1034648: postinst runs linux-update-symlinks before initrd exists Joey Hess <id@joeyh.name> - 2023-04-20 22:20 +0200
    Processed: Re: Bug#1034648: postinst runs linux-update-symlinks  before initrd exists "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-04-22 17:30 +0200
    Bug#1034648: postinst runs linux-update-symlinks before initrd exists Ben Hutchings <ben@decadent.org.uk> - 2023-04-22 17:30 +0200
      Bug#1034648: postinst runs linux-update-symlinks before initrd exists Joey Hess <id@joeyh.name> - 2023-04-24 17:10 +0200
    Bug#1034648: marked as done (postinst runs linux-update-symlinks  before initrd exists) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-04-25 20:30 +0200

#78783 — Bug#1034648: postinst runs linux-update-symlinks before initrd exists

FromJoey Hess <id@joeyh.name>
Date2023-04-20 22:20 +0200
SubjectBug#1034648: postinst runs linux-update-symlinks before initrd exists
Message-ID<GmIV3-3mJZ-1@gated-at.bofh.it>

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

Source: linux
Version: 6.1.20-2
Severity: normal

I was upgrading a slow arm board and noticed this:

Setting up linux-image-6.1.0-7-armmp-lpae (6.1.20-2) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.18.0-4-armmp-lpae
I: /initrd.img.old is now a symlink to boot/initrd.img-5.18.0-4-armmp-lpae
I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-7-armmp-lpae
I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-7-armmp-lpae
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-7-armmp-lpae

It probably took 5 minutes to generate the initrd, and until then
/initrd.img was a dangling symlink. A power failure in this wide window would
not be fun.

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_WARN
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
see shy jo

[toc] | [next] | [standalone]


#78813 — Processed: Re: Bug#1034648: postinst runs linux-update-symlinks before initrd exists

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2023-04-22 17:30 +0200
SubjectProcessed: Re: Bug#1034648: postinst runs linux-update-symlinks before initrd exists
Message-ID<Gnnlv-3LtD-5@gated-at.bofh.it>
In reply to#78783
Processing control commands:

> tag -1 moreinfo
Bug #1034648 [src:linux] postinst runs linux-update-symlinks before initrd exists
Added tag(s) moreinfo.

-- 
1034648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034648
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#78815

FromBen Hutchings <ben@decadent.org.uk>
Date2023-04-22 17:30 +0200
Message-ID<Gnnlv-3LtD-3@gated-at.bofh.it>
In reply to#78783

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

Control: tag -1 moreinfo

On Thu, 2023-04-20 at 16:09 -0400, Joey Hess wrote:
> Source: linux
> Version: 6.1.20-2
> Severity: normal
> 
> I was upgrading a slow arm board and noticed this:
> 
> Setting up linux-image-6.1.0-7-armmp-lpae (6.1.20-2) ...
> I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.18.0-4-armmp-lpae
> I: /initrd.img.old is now a symlink to boot/initrd.img-5.18.0-4-armmp-lpae
> I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-7-armmp-lpae
> I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-7-armmp-lpae
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-6.1.0-7-armmp-lpae
> 
> It probably took 5 minutes to generate the initrd, and until then
> /initrd.img was a dangling symlink. A power failure in this wide window would
> not be fun.

This behaviour is intentional.  The expectation is that these symlinks
are used by programs that update the boot loader configuration later
on, and those will be run only after the initramfs has been generated.
What do you think will go wrong here?

Ben.

-- 
Ben Hutchings
Theory and practice are closer in theory than in practice - John Levine

[toc] | [prev] | [next] | [standalone]


#78856

FromJoey Hess <id@joeyh.name>
Date2023-04-24 17:10 +0200
Message-ID<Go5Zf-4dim-3@gated-at.bofh.it>
In reply to#78815

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

Ben Hutchings wrote:
> This behaviour is intentional.  The expectation is that these symlinks
> are used by programs that update the boot loader configuration later
> on, and those will be run only after the initramfs has been generated.
> What do you think will go wrong here?

Ok, I am probably wrong in my concern then.

-- 
see shy jo

[toc] | [prev] | [next] | [standalone]


#78863 — Bug#1034648: marked as done (postinst runs linux-update-symlinks before initrd exists)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2023-04-25 20:30 +0200
SubjectBug#1034648: marked as done (postinst runs linux-update-symlinks before initrd exists)
Message-ID<GovAl-4tzr-3@gated-at.bofh.it>
In reply to#78783

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

Your message dated Tue, 25 Apr 2023 20:04:01 +0200
with message-id <d1e561e9e80c3bf457fda006d23654be993b5e79.camel@decadent.org.uk>
and subject line Re: Bug#1034648: postinst runs linux-update-symlinks before initrd exists
has caused the Debian Bug report #1034648,
regarding postinst runs linux-update-symlinks before initrd exists
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1034648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034648
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


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


csiph-web