Unnamed repository
c82a453c67
Any block device can be mounted multiply on the different mount point. Once a mount point is mounted in bind mode, the general mount point can be unmounted. Thus kdump would not find the general mount point[1] to handle the path. The mount point, which is as general mount point, will be got by "fintmnt" previously. But the mntpoint may be incorrect, if the mntpoint is bind mount. In order to fix it to support bind mounted in atomic, we will add a judgement to comfirm the mntpoint is bind mounted, or not. For general mount, returning path is like following, if we use "findmnt". The returning is same as "findmnt -v". -bash-4.2# findmnt /var | tail -n 1 | awk '{print $2}' /dev/mapper/atomicos-root But for bind mount, returning path is like following, if we use "fintmnt". -bash-4.2# findmnt /var | tail -n 1 | awk '{print $2}' /dev/mapper/atomicos-root[/ostree/deploy/rhel-atomic-host/var] Use "findmnt -v" is like this: -bash-4.2# findmnt -v /var | tail -n 1 | awk '{print $2}' /dev/mapper/atomicos-root So we can determine the bind mount, if the returning is different between "findmnt" and "findmnt -v". [1] general mount point is a directory without being in bind mounted mode, just a normal directory. Signed-off-by: Minfei Huang <mhuang@redhat.com> Acked-by: Dave Young <dyoung@redhat.com> Acked-by: Baoquan He <bhe@redhat.com> |
||
---|---|---|
anaconda-addon | ||
.gitignore | ||
98-kexec.rules | ||
dracut-kdump-capture.service | ||
dracut-kdump-emergency.service | ||
dracut-kdump-error-handler.service | ||
dracut-kdump-error-handler.sh | ||
dracut-kdump.sh | ||
dracut-module-setup.sh | ||
dracut-monitor_dd_progress | ||
fadump-howto.txt | ||
kdump-dep-generator.sh | ||
kdump-in-cluster-environment.txt | ||
kdump-lib-initramfs.sh | ||
kdump-lib.sh | ||
kdump.conf | ||
kdump.conf.5 | ||
kdump.service | ||
kdump.sysconfig | ||
kdump.sysconfig.i386 | ||
kdump.sysconfig.ppc64 | ||
kdump.sysconfig.ppc64le | ||
kdump.sysconfig.s390x | ||
kdump.sysconfig.x86_64 | ||
kdumpctl | ||
kexec-kdump-howto.txt | ||
kexec-tools-2.0.3-disable-kexec-test.patch | ||
kexec-tools-2.0.7-kexec-ppc64-disabling-exception-handling-when-buildi.patch | ||
kexec-tools-2.0.7-kexec-ppc64-move-to-device-tree-version-17.patch | ||
kexec-tools-2.0.7-ppc64-kdump-Fix-ELF-header-endianess.patch | ||
kexec-tools-2.0.7-Provide-an-option-to-use-new-kexec-system-call.patch | ||
kexec-tools.spec | ||
mkdumprd | ||
mkdumprd.8 | ||
README | ||
rhcrashkernel-param | ||
sources | ||
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