Oops..forgot to add subject-prefix as V5. Kindly treat this series as "PATCH V5"

On Fri, Apr 29, 2016 at 12:20 PM, Pratyush Anand panand@redhat.com wrote:

Kexec-tools should be able to recognize if a dump target is reformatted, or dump path mounts another device.

Changes since v4:

• patch 4/5 is a new change
• patch 4/4 of V3 is now 4/5. There has been many modifications in this patch. It includes feedback from Baoquan and Xunlei. Have also done some

modification to recognize changes related to minix and NFS filesystem as well. Infact, whole structure of function is_fs_uuid_changed() has been modified. Now it has been renamed as is_dump_fs_modified() to suit it better. Although I have tested it rigorously, but still a careful review of is_dump_fs_modified() will be helpful.

Changes since v3:

• "$ret" unquoted
• No message for "$system_modified" != "0"
• image_time is now global
• is_dump_target_modified has been renamed as is_fs_uuid_changed

Changes since v2: -- now is_system_modified returns 2 in case of invalid modification, 1 in case of valid modification and 0 in case of no modification. -- file modification check has been moved to is_system_modified now -- variables have been put under "" in if condition check

Changes since v1: -- Local variable is defined in shell function now -- raw target does not take persistent names "by-uuid" now -- dracut arguments grep is more robust -- When no UUID then warn and return

Pratyush Anand (5): mkdumprd: do not lookup in by-uuid dirs for raw device's persistent name kdumpctl: force rebuild in case of dynamic system modification kdumpctl: Move file modification check logic in is_system_modified() mkdumprd: move to_dev_name() to kdump-lib.sh kdumpctl: force rebuild in case of file system is modified

kdump-lib.sh | 14 +++++ kdumpctl | 173 ++++++++++++++++++++++++++++++++++++++++++++++++++--------- mkdumprd | 28 ++++------ 3 files changed, 171 insertions(+), 44 deletions(-)

-- 2.5.5