| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1399469234-54925-1-git-send-email-sdu.liu@huawei.com> Date: Wed, 7 May 2014 21:27:12 +0800 From: Liu Hua <sdu.liu@...wei.com> To: <linux@....linux.org.uk>, <kumagai-atsushi@....nes.nec.co.jp> CC: <will.deacon@....com>, <kexec@...ts.infradead.org>, <linux-kernel@...r.kernel.org>, <wangnan0@...wei.com>, <peifeiyue@...wei.com>, <sdu.liu@...wei.com>, <liusdu@....com> Subject: [RFC PATCH 0/2] transfer sparse memory related values Now different platforms may have different SECTION_SIZE_BITS and MAX_PHYSMEM_BITS. But linux passes nothing related to the vmcore. User space tools such as makedumpfile needs these to deal with the vmcore. So we must define these when compiling. So if we deal with aother vmcore. We may need to recompile the tools. These patch series make kernel pass related infomation to the user space tools, via vmcore. And makedumpfile can get these when parsing vmcore. So the makdumpfile becomes more compatible to vmcore with different section size. Liu Hua (1): kdump: add sparse memory related values to vmcore makedumpfile: get additional information from vmcore kernel/kexec.c | 3 +++ makedumpfile.c | 17 +++++++++++++++++ makedumpfile.h | 2 ++ 3 files changed, 22 insertions(+) -- 1.9.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists