Unnamed repository
90da030e61
Resolves: bz2069200 Upstream: github.com/makedumpfile/makedumpfile.git Conflicts: None commit feae3d1754d2b0788ce1f18b0cd4b40098ff52ff Author: Philipp Rudo <prudo@redhat.com> Date: Mon Mar 14 17:04:29 2022 +0100 [PATCH v2 1/3] add generic cycle detection In order to work makedumpfile needs to interpret data read from the dump. This can cause problems as the data from the dump cannot be trusted (otherwise the kernel wouldn't have panicked in the first place). This also means that every loop which stop condition depend on data read from the dump has a chance to loop forever. Thus add a generic cycle detection mechanism that allows to detect and handle such situations appropriately. For cycle detection use Brent's algorithm [1] as it has constant memory usage. With this it can also be used in the kdump kernel without the danger that it runs oom when iterating large data structures. Furthermore it only depends on some pointer arithmetic. Thus the performance impact (as long as no cycle was detected) should be comparatively small. [1] https://en.wikipedia.org/wiki/Cycle_detection#Brent's_algorithm Suggested-by: Dave Wysochanski <dwysocha@redhat.com> Signed-off-by: Philipp Rudo <prudo@redhat.com> Reviewed-and-tested-by: Dave Wysochanski <dwysocha@redhat.com> Signed-off-by: Philipp Rudo <prudo@redhat.com> |
||
---|---|---|
tests | ||
.editorconfig | ||
.gitignore | ||
60-kdump.install | ||
92-crashkernel.install | ||
98-kexec.rules | ||
98-kexec.rules.ppc64 | ||
crashkernel-howto.txt | ||
dracut-early-kdump-module-setup.sh | ||
dracut-early-kdump.sh | ||
dracut-fadump-init-fadump.sh | ||
dracut-fadump-module-setup.sh | ||
dracut-kdump-capture.service | ||
dracut-kdump-emergency.service | ||
dracut-kdump-emergency.target | ||
dracut-kdump.sh | ||
dracut-module-setup.sh | ||
dracut-monitor_dd_progress | ||
early-kdump-howto.txt | ||
fadump-howto.txt | ||
gating.yaml | ||
kdump-dep-generator.sh | ||
kdump-in-cluster-environment.txt | ||
kdump-lib-initramfs.sh | ||
kdump-lib.sh | ||
kdump-logger.sh | ||
kdump-migrate-action.sh | ||
kdump-restart.sh | ||
kdump-udev-throttler | ||
kdump.conf | ||
kdump.conf.5 | ||
kdump.service | ||
kdump.sysconfig | ||
kdump.sysconfig.aarch64 | ||
kdump.sysconfig.i386 | ||
kdump.sysconfig.ppc64 | ||
kdump.sysconfig.ppc64le | ||
kdump.sysconfig.s390x | ||
kdump.sysconfig.x86_64 | ||
kdumpctl | ||
kdumpctl.8 | ||
kexec-kdump-howto.txt | ||
kexec-tools-2.0.22-01-s390_handle_R_390_PLT32DBL_reloc_entries_in_machine_apply_elf_rel_.patch | ||
kexec-tools-2.0.23-01-_PATCH_v2_1_3_add_generic_cycle_detection.patch | ||
kexec-tools-2.0.23-makedumpfile-sadump-kaslr-fix-failure-of-calculating-kaslr_.patch | ||
kexec-tools.spec | ||
live-image-kdump-howto.txt | ||
mkdumprd | ||
mkdumprd.8 | ||
mkfadumprd | ||
README | ||
sources | ||
supported-kdump-targets.txt | ||
zanata-notes.txt |
Adding a patch to kexec-tools ============================= There is a mailing list kexec@lists.fedoraproject.org where all the dicussion related to fedora kexec-tools happen. All the patches are posted there for inclusion and committed to kexec-tools after review. So if you want your patches to be included in fedora kexec-tools package, post these to kexec@lists.fedoraproject.org. One can subscribe to list and browse through archives here. https://admin.fedoraproject.org/mailman/listinfo/kexec