Your message dated Wed, 07 Jul 2021 21:57:34 +0200
with message-id <[email protected]>
and subject line Re: Bug#984650: update-initramfs fails when 
/etc/systemd/network/99-default.link is symlink to /dev/null
has caused the Debian Bug report #984650,
regarding update-initramfs fails if there is a symlink to /dev/zero in 
/etc/systemd/network
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 [email protected]
immediately.)


-- 
984650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984650
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.133+deb10u1
Severity: important

When one disables the "Predicatble Network InterfaceNames" 
by making /lib/systemd/network/99-default.link a symlink to /dev/zero then
update-initramfs will fail as the copy of this symlink will fill-up all space
available in /var/tmp and makes it impossible to install any kernel image

the culprit is the following command executed by update-initramfs:

        find /etc/systemd/network -name *.link -execdir cp -pt /var/tmp/ {} +

As it (and should) dereference de symlink, it reads zero bytes from /dev/null 
until the disk is full.

Changing the symlink to a zero byte file resolved the issue for me but as this
approach is one of the recommended approaches to disable predicatble network
interface names (see [1]) others may also bump into this.

[1] https://wiki.debian.org/NetworkInterfaceNames#How_to_get_it_back

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 6.9M Mar  6 14:31 /boot/initrd.img-4.19.0-13-amd64
-rw-r--r-- 1 root root 6.9M Mar  6 14:32 /boot/initrd.img-4.19.0-14-amd64
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.19.0-14-amd64 
root=UUID=8d33b150-7c84-4dd0-8893-06eab0e7b9d7 ro quiet

-- resume
RESUME=UUID=2db37a4d-80dd-46b3-aa4d-ff57862589ba
-- /proc/filesystems
        ext3
        ext2
        ext4

-- lsmod
Module                  Size  Used by
vmw_vsock_vmci_transport    32768  1
vsock                  40960  2 vmw_vsock_vmci_transport
ata_generic            16384  0
crct10dif_pclmul       16384  0
crc32_pclmul           16384  0
vmwgfx                331776  1
ttm                   126976  1 vmwgfx
ghash_clmulni_intel    16384  0
vmw_balloon            20480  0
drm_kms_helper        208896  1 vmwgfx
intel_rapl_perf        16384  0
joydev                 24576  0
pcspkr                 16384  0
drm                   495616  4 vmwgfx,drm_kms_helper,ttm
ahci                   40960  0
vmxnet3                69632  0
ata_piix               36864  0
libahci                40960  1 ahci
sg                     36864  0
libata                270336  4 ata_piix,libahci,ahci,ata_generic
vmw_vmci               81920  2 vmw_balloon,vmw_vsock_vmci_transport
i2c_piix4              24576  0
ac                     16384  0
button                 20480  0
ip_tables              28672  0
x_tables               45056  1 ip_tables
autofs4                49152  2
ext4                  745472  1
crc16                  16384  1 ext4
mbcache                16384  1 ext4
jbd2                  122880  1 ext4
crc32c_generic         16384  0
fscrypto               32768  1 ext4
ecb                    16384  0
crc32c_intel           24576  2
sd_mod                 61440  3
aesni_intel           200704  0
psmouse               172032  0
aes_x86_64             20480  1 aesni_intel
crypto_simd            16384  1 aesni_intel
cryptd                 28672  3 crypto_simd,ghash_clmulni_intel,aesni_intel
glue_helper            16384  1 aesni_intel
evdev                  28672  2
serio_raw              16384  0
vmw_pvscsi             28672  2
scsi_mod              249856  4 vmw_pvscsi,sd_mod,libata,sg

-- /etc/initramfs-tools/modules

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = no

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=auto
KEYMAP=n
COMPRESS=gzip
DEVICE=
NFSROOT=auto
RUNSIZE=10%

-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no

-- /sys/block
sda

-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:

/usr/share/initramfs-tools/hooks:
dmsetup
fsck
fuse
keymap
klibc-utils
kmod
resume
thermal
udev
zz-busybox


-- System Information:
Debian Release: 10.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-14-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.utf8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.utf8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages initramfs-tools depends on:
ii  initramfs-tools-core  0.133+deb10u1
ii  linux-base            4.6

initramfs-tools recommends no packages.

Versions of packages initramfs-tools suggests:
ii  bash-completion  1:2.8-6

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi Frederik

On Tue, 16 Mar 2021 19:42:48 +0100 Michael Biebl <[email protected]> wrote:
> 
> On Sat, 6 Mar 2021 17:22:17 +0100 Frederik Lindenaar
> <[email protected]> wrote:

> > Why not use a cp -aLt <directory> {} instead to prevent this?
> > 
> 
> This wouldn't produce the right result afaics. If you mask a file by
> symlinking it to /dev/null, the current code produces a file with zero-
> size (which is also acceptable for masking files).
> 
> If you dereference (-L), you instead copy a character device, which is
> not the same as a zero-sized file.
> 
> We also have to keep in mind, that if a .link file in
> /etc/system/network, pointing to some link elsewhere, we probably do
> want to resolve that and not copy a dangling symlink.
> 
> The current code is already ugly as it is. I'm not sure, adding more
> corner cases is a good idea. That said, I'm open to suggestions. The
> code must
> 
> - make sure files with the same name in /etc/systemd/network take
> precedence of files in /lib/systemd/network
> - correctly handle masked .link files (i.e. files pointing at
> /dev/null)
> - correctly handle the case that /etc/systemd/network doesn't exist or
> itself is a symlink
> 
> I'm happy to take a patch for that.

No such patch was provided, so I'm closing this bug report at this point.
I'm fine with this bug being reopened if someone has interest in this and
produces a patch / MR.

Regards,
Michael

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply via email to