7e10236038
This patch updates kexec-tools from 2.0.15 to 2.0.21 (and its supporting software package makedumpfile from 1.6.2 to 1.6.9) for compatibility with the newer v5.10 kernel. This commit clones the kexec-tools package's supporting files from commit 26a7a543427eac59ed39728466f3d95d320f735a in the CentOS RPM packaging git repository. Links for reference: -26a7a54342-26a7a54342Please note that this patch causes the build system to pull in and extract an SRPM file to acquire: kdump-anaconda-addon-003-29-g4c517c5.tar.gz This is done for security, because the only public reference to commit 4c517c5 is on a Red Hat developer's personal Github account: https://github.com/ryncsn/kdump-anaconda-addon/commits/rhel-7 kexec-tools package's supporting files cloned by this commit trigger a large number of shell script linting errors. Given that the shell scripts in question are inherited from upstream (i.e., CentOS 7), the "files" directory of this package is excluded from automated linting via the changes in tox.ini. Verification: A kexec-tools RPM package built with this commit was installed onto an existing StarlingX system. A vmcore file was succesfully collected from a kernel crash triggered with /proc/sysrq-trigger. A recent version of the crash utility was found to succesfully parse the collected vmcore file. Credits: Thanks to Jiping Ma for helping with cleaning up and publishing an earlier version of this patch. Story: 2008921 Task: 43040 Depends-On: https://review.opendev.org/c/starlingx/tools/+/805127 Signed-off-by: Jiping Ma <jiping.ma2@windriver.com> Signed-off-by: M. Vefa Bicakci <vefa.bicakci@windriver.com> Change-Id: Idc4e523610e4c09259300c8b67ea5e0fbe59c611
20 lines
615 B
Plaintext
20 lines
615 B
Plaintext
Metadata-Version: 1.0
|
|
Name: kexec-tools
|
|
Version: 2.0.21
|
|
Summary: The kexec/kdump userspace component.
|
|
Home-page: https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/
|
|
Author:
|
|
Author-email:
|
|
License: GPLv2
|
|
|
|
Description:
|
|
/sbin/kexec is a user space utility for loading another kernel
|
|
and asking the currently running kernel to do something with it.
|
|
A currently running kernel may be asked to start the loaded
|
|
kernel on reboot, or to start the loaded kernel after it panics.
|
|
|
|
The panic case is useful for having an intact kernel for writing
|
|
crash dumps. But other uses may be imagined.
|
|
|
|
Platform: UNKNOWN
|