Your message dated Thu, 27 Dec 2018 13:55:36 +0000
with message-id <[email protected]>
and subject line Bug#917124: fixed in systemd 240-2
has caused the Debian Bug report #917124,
regarding linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume
containing / not created on system startup
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.)
--
917124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917124
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:linux
Version: 4.19.12-1
Severity: important
Hi,
[I'm not sure whether this is the right package to report against - feel
free to reassign as appropriate.]
I have / on a luks volume, mounted with dm-crypt (automatically,
via /etc/fstab - /etc/crypttab). As recently as kernel 4.18.0-3,
everything was normal. With 4.19.0-1, the volume mounts, and the
system seems basically functional - but /dev/mapper is empty aside for
'control'!
~# ls -al /dev/mapper/
total 0
drwxr-xr-x 2 root root 60 Dec 23 23:32 .
drwxr-xr-x 18 root root 3340 Dec 23 23:32 ..
crw------- 1 root root 10, 236 Dec 23 23:32 control
'mount' shows that the dm-crypt mount is actually present:
~# mount | grep sda
/dev/mapper/sda2_crypt on / type ext4 (rw,relatime,errors=remount-ro)
/dev/sda1 on /boot type ext4 (rw,relatime)
~#
This situation causes update-initramfs to fail:
~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.19.0-1-amd64
mkinitramfs: failed to determine device for /
mkinitramfs: workaround is MODULES=most, check:
grep -r MODULES /etc/initramfs-tools
Error please report bug on initramfs-tools
Include the output of 'mount' and 'cat /proc/mounts'
update-initramfs: failed for /boot/initrd.img-4.19.0-1-amd64 with 1.
~#
Which in turn is causing things like kernel updates to fail ...
Running 'dmsetup mknodes' manually adds the proper symlink.
Additionally, running cryptsetup on an additional encrypted luks volume
results in the proper symlink creation for that volume.
-- Package-specific info:
** Version:
Linux version 4.19.0-1-amd64 ([email protected]) (gcc version
8.2.0 (Debian 8.2.0-13)) #1 SMP Debian 4.19.12-1 (2018-12-22)
** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-1-amd64
root=UUID=db4c898d-57d7-4b0b-8dc1-c1622e451d68 ro quiet crashkernel=384M-:128M
** Tainted: WOE (12800)
* Taint on warning.
* Out-of-tree module has been loaded.
* Unsigned module has been loaded.
** Kernel log:
Unable to read kernel log; any relevant messages should be attached
** Model information
sys_vendor: LENOVO
product_name: 20E2CTO1WW
product_version: ThinkPad W550s
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: N11ET42W (1.18 )
board_vendor: LENOVO
board_name: 20E2CTO1WW
board_version: SDK0J40705 WIN
** Loaded modules:
cpuid
ctr
algif_skcipher
af_alg
ses
enclosure
scsi_transport_sas
nft_chain_route_ipv4
xt_CHECKSUM
nft_chain_nat_ipv4
ipt_MASQUERADE
nf_nat_ipv4
nf_nat
xt_conntrack
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
libcrc32c
ipt_REJECT
nf_reject_ipv4
nft_counter
xt_tcpudp
nft_compat
tun
bridge
stp
llc
acpi_call(OE)
btusb
btrtl
btbcm
btintel
bluetooth
drbg
ebtable_filter
ebtables
devlink
ansi_cprng
ecdh_generic
nf_tables
nfnetlink
cpufreq_conservative
cpufreq_userspace
cpufreq_powersave
ipmi_devintf
ipmi_msghandler
uas
usb_storage
nls_utf8
cifs
ccm
dns_resolver
fscache
snd_hda_codec_hdmi
bbswitch(OE)
arc4
intel_rapl
x86_pkg_temp_thermal
intel_powerclamp
iwlmvm
coretemp
kvm_intel
mac80211
iTCO_wdt
kvm
rtsx_pci_sdmmc
mmc_core
rtsx_pci_ms
memstick
iTCO_vendor_support
wmi_bmof
i915
irqbypass
crct10dif_pclmul
crc32_pclmul
ghash_clmulni_intel
intel_cstate
snd_hda_codec_realtek
intel_uncore
drm_kms_helper
snd_hda_codec_generic
intel_rapl_perf
ehci_pci
xhci_pci
ehci_hcd
iwlwifi
xhci_hcd
sg
snd_hda_intel
mei_me
drm
snd_hda_codec
mei
cfg80211
e1000e
pcspkr
snd_hda_core
usbcore
rtsx_pci
joydev
snd_hwdep
snd_pcm
i2c_i801
i2c_algo_bit
usb_common
lpc_ich
thinkpad_acpi
intel_pch_thermal
snd_timer
wmi
nvram
ac
tpm_tis
snd
tpm_tis_core
tpm
soundcore
rfkill
rng_core
battery
video
pcc_cpufreq
button
parport_pc
ppdev
lp
parport
sunrpc
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
fscrypto
ecb
dm_crypt
dm_mod
sd_mod
crc32c_intel
ahci
libahci
aesni_intel
libata
aes_x86_64
crypto_simd
cryptd
scsi_mod
psmouse
glue_helper
evdev
serio_raw
thermal
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-image-4.19.0-1-amd64 depends on:
ii initramfs-tools [linux-initramfs-tool] 0.132
ii kmod 25-2
ii linux-base 4.5
Versions of packages linux-image-4.19.0-1-amd64 recommends:
ii apparmor 2.13.1-3+b1
ii firmware-linux-free 3.4
ii irqbalance 1.5.0-0.1
Versions of packages linux-image-4.19.0-1-amd64 suggests:
pn debian-kernel-handbook <none>
ii grub-pc 2.02+dfsg1-9
pn linux-doc-4.19 <none>
Versions of packages linux-image-4.19.0-1-amd64 is related to:
pn firmware-amd-graphics <none>
pn firmware-atheros <none>
pn firmware-bnx2 <none>
pn firmware-bnx2x <none>
pn firmware-brcm80211 <none>
pn firmware-cavium <none>
pn firmware-intel-sound <none>
pn firmware-intelwimax <none>
pn firmware-ipw2x00 <none>
pn firmware-ivtv <none>
ii firmware-iwlwifi 20180825+dfsg-1
pn firmware-libertas <none>
pn firmware-linux-nonfree <none>
pn firmware-misc-nonfree <none>
pn firmware-myricom <none>
pn firmware-netxen <none>
pn firmware-qlogic <none>
pn firmware-realtek <none>
pn firmware-samsung <none>
pn firmware-siano <none>
pn firmware-ti-connectivity <none>
pn xen-hypervisor <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 240-2
We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Biebl <[email protected]> (supplier of updated systemd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 27 Dec 2018 14:03:57 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote
systemd-coredump systemd-tests libpam-systemd libnss-myhostname
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 240-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
<[email protected]>
Changed-By: Michael Biebl <[email protected]>
Description:
libnss-myhostname - nss module providing fallback resolution for the current
hostname
libnss-mymachines - nss module to resolve hostnames for local container
instances
libnss-resolve - nss module to resolve names via systemd-resolved
libnss-systemd - nss module providing dynamic user and group name resolution
libpam-systemd - system and service manager - PAM module
libsystemd-dev - systemd utility library - development files
libsystemd0 - systemd utility library
libudev-dev - libudev development files
libudev1 - libudev shared library
libudev1-udeb - libudev shared library (udeb)
systemd - system and service manager
systemd-container - systemd container/nspawn tools
systemd-coredump - tools for storing and retrieving coredumps
systemd-journal-remote - tools for sending and receiving remote journal logs
systemd-sysv - system and service manager - SysV links
systemd-tests - tests for systemd
udev - /dev/ and hotplug management daemon
udev-udeb - /dev/ and hotplug management daemon (udeb)
Closes: 917124 917167 917195 917215
Changes:
systemd (240-2) unstable; urgency=medium
.
* Pass seperate dev_t var to device_path_parse_major_minor.
Fixes FTBFS on mips/mipsel (MIPS/O32). (Closes: #917195)
* test-json: Check absolute and relative difference in floating point test.
Fixes FTBFS due to test-suite failures on armel, armhf and hppa.
(Closes: #917215)
* sd-device: Fix segfault when error occurs in
device_new_from_{nulstr,strv}()
Fixes a segfault in systemd-udevd when debug logging is enabled.
* udev-event: Do not read stdout or stderr if the pipefd is not created.
This fixes problems with device-mapper symlinks no longer being created
or certain devices not being marked as ready. (Closes: #917124)
* Don't bump fs.nr_open in PID 1.
In v240, systemd bumped fs.nr_open in PID 1 to the highest possible
value. Processes that are spawned directly by systemd, will have
RLIMIT_NOFILE be set to 512K (hard).
pam_limits in Debian defaults to "set_all", i.e. for limits which are
not explicitly configured in /etc/security/limits.conf, the value from
PID 1 is taken, which means for login sessions, RLIMIT_NOFILE is set to
the highest possible value instead of 512K. Not every software is able
to deal with such an RLIMIT_NOFILE properly.
While this is arguably a questionable default in Debian's pam_limit,
work around this problem by not bumping fs.nr_open in PID 1.
(Closes: #917167)
Checksums-Sha1:
9b1dce69b7d583347c7233720751438bb3849c4b 4898 systemd_240-2.dsc
0eff82b7240cf044c2ffa85dd2bd260615e21e52 140384 systemd_240-2.debian.tar.xz
231cd1d9f753510d633b56caffab0a794563794c 9077 systemd_240-2_source.buildinfo
Checksums-Sha256:
7a64ed3bb00733d83c4356a5c5454a32e275e7c133df1a00e74ba1d2df216076 4898
systemd_240-2.dsc
540d822a3a3aafdf6f26d0b5fc2ed8532f943f4748cf52f36f3f45acd337b1fc 140384
systemd_240-2.debian.tar.xz
889ba86df70d40577609fd9daa137366d925df11501313b8e84210f392849089 9077
systemd_240-2_source.buildinfo
Files:
5b42fd8e8d5c0f5e4646687d00cbdfc0 4898 admin optional systemd_240-2.dsc
6769149017a0a1dbf2dc0f16924b2ab1 140384 admin optional
systemd_240-2.debian.tar.xz
40f134cdfb3264c5a0f731b96bae8a61 9077 admin optional
systemd_240-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlwk1SUACgkQauHfDWCP
ItzNEQ/6A22sbhxJVuGlnOBzJpTp+2cd+fia88XFWnTf8VA8L6Zf/hVlmdmMf1JY
tHwgj1DxpDNDhgCGWbLOykbux8ZjaSfodgLiRbvUmtKdDZ+KZmavMdHYTGtAWgUo
dswnCnUhgO1csE6GgPFNdZS/q2gBczkTDruuNgamlBdgZ2BbmFbYd7kiqeKHNwRa
VwsxfaU7fe+OUw7cdObbwqVpJhIhfZ4ubcKIPrJlM90TcHa5CSVnvZW1xf9Fi2lv
MgNwZN3cBl7531R9Y6t+ytsNdV7qM4xxL8pE0aFGXG5RSl51+jb8LJ/BeorkbzFT
YeGfea2mzoLAHJInokeyJEqc19zIe2/KWN54z4ZVHd7HA4dNbNGo7EI4IIBVcaeC
F7PenSO1FWxZCklf1EArXXLuU3Oqc2anDtA0IzQHCBOkP7vQsr9LsU2SGCrU9pOd
CCL3IP5t8sq6hgl4lXU5cdhSTpZDlkou+mdmWeYo2oyfIl399vUHkj6QS+p6aQAj
WEtD4RPgDY1B2IsFCN4r/0P7xIdIyL8anVsvq0KFJ6j1gbz9p4zCl9VGZprNnuac
tsZ6/H0dZBI4CK1gPk37fILO48csi04H3cX4Z1+ZWmHNEChtj5oChWhemrW6jaff
UQ+eyKcAiMgK480yJkZzJCYFQ32YqVrYkWsCRbZb+8gre4AJWh4=
=JlKn
-----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
