Re: [RFC PATCH 0/8] introduce a mechanism for doing something regarding the dump target

We add a generic dump target hook for kdump, supposed to monitor all the devices mounted by kdump. PATCH6 implements the basic framework, add a hook kdump_target_hook(), and provide a generic helper kdump_target_check() for use(must use it under mkdump/dracut). The first five patches are prerequisites for the mechanism, this will ensure us only have one device(our dump target) mounted after kdump boot, there still are corner cases like the special "x-initrd.mount" in /etc/fstab, we can discuss it further to see if we should mount it by kdump or handle it?

PATCH7 is an application of this mechanism(add the "lvm_linear" checklist), if the dump target is linear type lvm volume, we reduce the "reserved_memory" in "/etc/lvm/lvm.conf" from 8MB to 1MB(we discussed this with lvm team, they agree that we can safely set it to 1MB in case of only one lvm linear target). PATCH8 is another application(add the "lvm" checklist) to remove "lvm" dracut module when no lvm target needed by kdump. Xunlei Pang (8): kdumpctl: fix a bug in remove_cmdline_param() kdumpctl: remove "root=X" for kdump boot kdumpctl: fix the rebuild issue after removing "root=X" Revert "kdumpctl: filter 'root' kernel parameter when running in live images" kdumpctl: move is_fadump_capable() into kdump-lib.sh mkdumprd: add a generic hook for the dump target mkdumprd: reduce lvm2 memory in case of linear volume mkdumprd: omit "lvm" dracut module if no lvm target dracut-module-setup.sh | 6 +++ dracut-process-lvmconf.sh | 6 +++ kdump-lib.sh | 25 +++++++++ kdumpctl | 36 +++++-------- kexec-tools.spec | 3 ++ mkdumprd | 128 +++++++++++++++++++++++++++++++++++++++------- 6 files changed, 163 insertions(+), 41 deletions(-) create mode 100644 dracut-process-lvmconf.sh