The patch titled
kdump-add-is_vmcore_usable-and-vmcore_unusable update
has been added to the -mm tree. Its filename is
kdump-add-is_vmcore_usable-and-vmcore_unusable-update.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: kdump-add-is_vmcore_usable-and-vmcore_unusable update
From: Simon Horman <horms@xxxxxxxxxxxx>
I don't think this change was described at all...
Signed-off-by: Simon Horman <horms@xxxxxxxxxxxx>
Cc: Vivek Goyal <vgoyal@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/crash_dump.h | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)
diff -puN include/linux/crash_dump.h~kdump-add-is_vmcore_usable-and-vmcore_unusable-update include/linux/crash_dump.h
--- a/include/linux/crash_dump.h~kdump-add-is_vmcore_usable-and-vmcore_unusable-update
+++ a/include/linux/crash_dump.h
@@ -39,15 +39,11 @@ static inline int is_kdump_kernel(void)
{
return (elfcorehdr_addr != ELFCORE_ADDR_MAX) ? 1 : 0;
}
-#else /* !CONFIG_CRASH_DUMP */
-static inline int is_kdump_kernel(void) { return 0; }
-#endif /* CONFIG_CRASH_DUMP */
-#ifdef CONFIG_PROC_VMCORE
/* is_vmcore_usable() checks if the kernel is booting after a panic and
* the vmcore region is usable.
*
- * This makes use of the fact that due to alignment 1 is not
+ * This makes use of the fact that due to alignment -2ULL is not
* a valid pointer, much in the vain of IS_ERR(), except
* dealing directly with an unsigned long long rather than a pointer.
*/
@@ -66,7 +62,9 @@ static inline void vmcore_unusable(void)
if (is_kdump_kernel())
elfcorehdr_addr = ELFCORE_ADDR_ERR;
}
-#endif /* CONFIG_PROC_VMCORE */
+#else /* !CONFIG_CRASH_DUMP */
+static inline int is_kdump_kernel(void) { return 0; }
+#endif /* CONFIG_CRASH_DUMP */
extern unsigned long saved_max_pfn;
#endif /* LINUX_CRASHDUMP_H */
_
Patches currently in -mm which might be from horms@xxxxxxxxxxxx are
linux-next.patch
kdump-make-elfcorehdr_addr-independent-of-config_proc_vmcore.patch
kdump-update-elfcorehdr-documentation-to-reflect-supported-architectures.patch
kdump-use-is_kdump_kernel-in-sba_init.patch
kdump-add-is_vmcore_usable-and-vmcore_unusable.patch
kdump-add-is_vmcore_usable-and-vmcore_unusable-update.patch
kdump-use-is_vmcore_usable-and-vmcore_unusable-in-reserve_elfcorehdr.patch
kdump-ia64-always-reserve-elfcore-header-memory-in-crash-kernel.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
