Hello community, here is the log from the commit of package crash for openSUSE:Factory checked in at 2020-04-15 19:56:19 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/crash (Old) and /work/SRC/openSUSE:Factory/.crash.new.2738 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "crash" Wed Apr 15 19:56:19 2020 rev:160 rq:794163 version:7.2.8 Changes: -------- --- /work/SRC/openSUSE:Factory/crash/crash.changes 2020-02-04 19:58:15.113493027 +0100 +++ /work/SRC/openSUSE:Factory/.crash.new.2738/crash.changes 2020-04-15 19:56:25.097659836 +0200 @@ -1,0 +2,12 @@ +Wed Apr 8 09:42:08 UTC 2020 - Michal Suchanek <[email protected]> + +- Add crash-fix-kmem-sS-for-caches-created-during-SLUB-bootstrap.patch + Fix "kmem -[sS]" for caches created during SLUB bootstrap (bsc#1164815 ltc#182973). + +------------------------------------------------------------------- +Wed Apr 1 06:28:37 UTC 2020 - Michal Suchanek <[email protected]> + +- Add crash-Fix-for-reading-compressed-kdump-dumpfiles-from-syst.patch + Fix integer overflow with large memory configuration (bsc#1168233 ltc#184660). + +------------------------------------------------------------------- New: ---- crash-Fix-for-reading-compressed-kdump-dumpfiles-from-syst.patch crash-fix-kmem-sS-for-caches-created-during-SLUB-bootstrap.patch ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ crash.spec ++++++ --- /var/tmp/diff_new_pack.yGsBVy/_old 2020-04-15 19:56:26.737661067 +0200 +++ /var/tmp/diff_new_pack.yGsBVy/_new 2020-04-15 19:56:26.741661070 +0200 @@ -89,6 +89,8 @@ Patch16: eppic-support-arm64.patch Patch21: %{name}-allow-use-of-sadump-captured-KASLR-kernel.patch Patch24: %{name}-s390-autodetect-kaslr.patch +Patch25: %{name}-Fix-for-reading-compressed-kdump-dumpfiles-from-syst.patch +Patch26: %{name}-fix-kmem-sS-for-caches-created-during-SLUB-bootstrap.patch Patch90: %{name}-sial-ps-2.6.29.diff BuildRequires: bison BuildRequires: flex @@ -285,6 +287,8 @@ %patch13 -p1 %patch21 -p1 %patch24 -p1 +%patch25 -p1 +%patch26 -p1 %if %{have_snappy} %patch15 -p1 %endif ++++++ crash-Fix-for-reading-compressed-kdump-dumpfiles-from-syst.patch ++++++ >From b80b16549e24769c7d5fe3a10c4b1a1c4b5161f3 Mon Sep 17 00:00:00 2001 From: Dave Anderson <[email protected]> Date: Mon, 23 Mar 2020 15:52:11 -0400 Subject: [PATCH] Fix for reading compressed kdump dumpfiles from systems with physical memory located at extraordinarily high addresses. In a system with a physical address range from 0x602770ecf000 to 0x6027ffffffff, the crash utility fails during session initialization due to an integer overflow, ending with the error message "crash: vmlinux and vmcore do not match!". ([email protected]) References: bsc#1168233 ltc#184660 Upstream: merged Git-commit: b80b16549e24769c7d5fe3a10c4b1a1c4b5161f3 --- diskdump.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/diskdump.c b/diskdump.c index e88243e616cc..328c932dad5a 100644 --- a/diskdump.c +++ b/diskdump.c @@ -233,7 +233,7 @@ clean_diskdump_data(void) } static inline int -get_bit(char *map, int byte, int bit) +get_bit(char *map, unsigned long byte, int bit) { return map[byte] & (1<<bit); } @@ -694,7 +694,7 @@ restart: dd->max_mapnr = header->max_mapnr; /* read memory bitmap */ - bitmap_len = block_size * header->bitmap_blocks; + bitmap_len = (off_t)block_size * header->bitmap_blocks; dd->bitmap_len = bitmap_len; offset = (off_t)block_size * (1 + header->sub_hdr_size); @@ -744,7 +744,7 @@ restart: memcpy(dd->dumpable_bitmap, dd->bitmap, bitmap_len); dd->data_offset - = (1 + header->sub_hdr_size + header->bitmap_blocks) + = (1UL + header->sub_hdr_size + header->bitmap_blocks) * header->block_size; dd->header = header; -- 2.23.0 ++++++ crash-fix-kmem-sS-for-caches-created-during-SLUB-bootstrap.patch ++++++ >From 50f39247d80519c71d1f03984bc34aa476a9c2bd Mon Sep 17 00:00:00 2001 From: Hari Bathini <[email protected]> Date: Wed, 8 Apr 2020 11:38:23 +0200 Subject: [PATCH] fix "kmem -[sS]" for caches created during SLUB bootstrap References: bsc#1164815 ltc#182973 https://www.redhat.com/archives/crash-utility/2020-April/msg00029.html Upstream: submitted Fix for "kmem -[sS]" options on Linux 4.14 and later kernels built with CONFIG_SLAB_FREELIST_HARDENED enabled. Without the patch, there will error messages of the type "kmem: <cache name> slab: <address> invalid freepointer: <obfuscated address>" for caches created during SLUB bootstrap, as they are likely to have s->random == 0. Signed-off-by: Hari Bathini <hbathini linux ibm com> --- memory.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memory.c b/memory.c index ccc29442c3f6..c2433ebe5e75 100644 --- a/memory.c +++ b/memory.c @@ -19244,7 +19244,7 @@ count_free_objects(struct meminfo *si, ulong freelist) static ulong freelist_ptr(struct meminfo *si, ulong ptr, ulong ptr_addr) { - if (si->random) + if (VALID_MEMBER(kmem_cache_random)) /* CONFIG_SLAB_FREELIST_HARDENED */ return (ptr ^ si->random ^ ptr_addr); else -- 2.23.0
