2 Commits

Author	SHA1	Message	Date
Steffen Maier	4b486e87cc	zdev/dracut: fix kdump build to integrate with site support ... This complements v2.27.0 commit 73c46a3056 ("zdev/dracut: fix kdump by only activating required devices"). On older distributions, the absence of zdev_id can cause the following harmless error messages for each udev event: (spawn)[387]: failed to execute '/lib/s390-tools/zdev_id' \ '/lib/s390-tools/zdev_id': No such file or directory Kdump is still functional nonetheless. As of v2.24.0 commit 2e89722ef0 ("zdev: make site specific udev-rule for ccw"), the invocations of chzdev within zdev/dracut/95zdev-kdump/module-setup.sh generate /etc/udev/rules.d/40-zdev-id.rules. And so even though zdev-kdump intentionally does not install zdev_id and its previous singular user zdev/udev/81-dpm.rules into the kdump initrd, because DPM device auto configuration is not desired in the kdump environment, zdev_id meanwhile has an additional functionality for site-support and the generated 40-zdev-id.rules calls /lib/s390-tools/zdev_id. By installing zdev_id into the kdump initrd, 40-zdev-id.rules can work without error. Fixes: 73c46a3056 ("zdev/dracut: fix kdump by only activating required devices") Reviewed-by: Alexander Egorenkov <egorenar@linux.ibm.com> Reviewed-by: Vineeth Vijayan <vneethv@linux.ibm.com> Signed-off-by: Steffen Maier <maier@linux.ibm.com> Signed-off-by: Jan Höppner <hoeppner@linux.ibm.com>	2023-08-04 13:10:00 +02:00
Steffen Maier	73c46a3056	zdev/dracut: fix kdump by only activating required devices ... This prevents out-of-memory (OOM) situations in the kdump crashkernel environment. Please note that the new dracut module 95zdev-kdump and the new library zdev-lib.sh need to be packaged into the same (core) (sub)package as 95zdev. This patch introduces a new dracut module "zdev-kdump", which is used instead of module "zdev" when building a kdump initrd: 1. Ignore all persistently configured block devices and disable zfcp auto LUN scanning => minimize the number of SCSI devices enabled during kdump. 2. Do not rely on chzdev's persistent configuration => work with systems that do not use chzdev for persistent device configuration. The detection of kdump is based on strict hostonly mode and on $IN_KDUMP. See also https://src.fedoraproject.org/rpms/kexec-tools commit 4eedcae5e154 ("dracut-module-setup.sh: don't include multipath-hostonly") and https://github.com/dracutdevs/dracut commits 35e86ac117ac ("Merge 90-multipath-hostonly and 90-multipath") a695250ec7db ("Introduce tri-state hostonly mode") and https://src.fedoraproject.org/rpms/kexec-tools/blob/rawhide/f/mkdumprd#_17 https://src.fedoraproject.org/rpms/kexec-tools/blob/rawhide/f/dracut-module-setup.sh#_23. The detection of kdump is also based on kdump_needed() in https://github.com/openSUSE/kdump/blob/master/dracut/module-setup.sh. Reviewed-by: Peter Oberparleiter <oberpar@linux.ibm.com> Signed-off-by: Steffen Maier <maier@linux.ibm.com> Signed-off-by: Jan Höppner <hoeppner@linux.ibm.com>	2023-03-03 09:58:40 +01:00