Hello community, here is the log from the commit of package crash for openSUSE:Factory checked in at 2020-04-22 20:54:20 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/crash (Old) and /work/SRC/openSUSE:Factory/.crash.new.2738 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "crash" Wed Apr 22 20:54:20 2020 rev:161 rq:796107 version:7.2.8 Changes: -------- --- /work/SRC/openSUSE:Factory/crash/crash.changes 2020-04-15 19:56:25.097659836 +0200 +++ /work/SRC/openSUSE:Factory/.crash.new.2738/crash.changes 2020-04-22 20:54:23.227556072 +0200 @@ -1,0 +2,12 @@ +Sat Apr 18 12:00:31 UTC 2020 - Michal Suchanek <[email protected]> + +- Make Factory ppc64 crash usable on both SLE 15 SP1 and releases before + SLE15 SP1 (bsc#1148197). This is only a workaround that requires to build + crash for each codestream separately. + +------------------------------------------------------------------- +Fri Apr 17 23:53:17 UTC 2020 - Michal Suchanek <[email protected]> + +- Drop crash-s390-autodetect-kaslr.patch which has been merged in 7.2.7. + +------------------------------------------------------------------- @@ -41,3 +53,5 @@ -- Upgrade source tarball to version 7.2.7 to support currently used - kernel versions. -- drop the following patch that is obsoleted by souce upgrade: +- Upgraded the source tarball to version 7.2.7. This is required + to support coredumps from currently used kernel versions in the + product (bsc#1159686). +- droped the patch obsoleted due to already being present in the + new source: @@ -72 +86 @@ -- Add patch for commit 326e1b8f83a4318b09033ef754f40c785aed5e68 +- Added patch for commit 326e1b8f83a4318b09033ef754f40c785aed5e68 @@ -79,2 +93,5 @@ -- Upgrade source tarball to version 7.2.6 -- drop patches obsoleted by version upgrade + Upgraded the source tarball to version 7.2.6 to bring better + support of version 5 kernels such as 5.3 in SLE-15-SP2 + (bsc#114706) + + Dropped the following patches obsoleted by the version upgrade: @@ -90,0 +108,13 @@ + crash-Fix-and-an-update-for-the-ipcs-command.patch + crash-update-recognition-of-x86_64-CPU_ENTRY_AREA.patch + + Re-aligned the following patches with the new version source: + crash-allow-use-of-sadump-captured-KASLR-kernel.patch + crash-debuginfo-compressed.patch + crash-make-emacs-default.diff + crash-sles9-time.patch + + Modified the following patches to integrate with version upgrade: + crash-compressed-booted-kernel.patch + crash-SLE15-SP1-With-Linux-4.19-rc1-up-MAX_PHYSMEM_BITS-to-128TB.patch + crash-SLE15-SP1-Fix-for-PPC64-kernel-virtual-address-translation-in.patch @@ -98 +127,0 @@ - * crash-stop_read_error_when_intent_is_retry.patch @@ -114,3 +143,7 @@ -- With a xen 4.11 dump crash will fail to start reporting "cannot - fill pcpu struct" and "cannot read cpu_info" due to xen changes - not tracked by crash updates. Fixed by including: +- Update for XEN dom0 changes in v4.11 that cause coredumps made + of a domU using virch on the dom0 to fail to load in the dom0 + version of crash reporting "crash: invalid kernel virtual address: + <address> type:fill_pcpu_struct", followed by "WARNING: cannot + fill pcpu_struct" and "crash: cannot read cpu_info" + (bsc#1124690 and bsc#1122594) + Added: @@ -118 +151,16 @@ - (bsc#1122594) + +------------------------------------------------------------------- +Fri Jan 11 15:07:52 UTC 2019 - [email protected] + +- Update the recognition of x86_64 CPU_ENTRY_AREA (bsc#1104743, bsc#1090127) + Added: + crash-update-recognition-of-x86_64-CPU_ENTRY_AREA.patch + +------------------------------------------------------------------- +Tue Dec 18 16:36:40 UTC 2018 - Michal Suchanek <[email protected]> + +- Fix SLE15 SP1 Incorrect vmcore generated (bsc#1119791). + Added: + crash-SLE15-SP1-With-Linux-4.19-rc1-up-MAX_PHYSMEM_BITS-to-128TB.patch + crash-SLE15-SP1-Fix-for-PPC64-kernel-virtual-address-translation-in.patch + This is not compatible with SLE15 and SLE12 SP4. @@ -124,0 +173,13 @@ + +------------------------------------------------------------------- +Wed Aug 8 11:02:28 UTC 2018 - [email protected] + +- Added: + crash-Fix-and-an-update-for-the-ipcs-command.patch + + The update is required for Linux 4.11 and greater kernels, which + reimplemented the IDR facility to use radix trees in kernel commit + 0a835c4f090af2c76fc2932c539c3b32fd21fbbb, titled "Reimplement IDR and IDA + using the radix tree". Without the patch, if any IPCS entry exists, the + command would fail with the message "ipcs: invalid structure member offset: + idr_top" (bsc#1092101) Old: ---- crash-s390-autodetect-kaslr.patch New: ---- crash-SLE15-SP1-Fix-for-PPC64-kernel-virtual-address-translation-in.patch crash-SLE15-SP1-With-Linux-4.19-rc1-up-MAX_PHYSMEM_BITS-to-128TB.patch crash-stop_read_error_when_intent_is_retry.patch ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ crash.spec ++++++ --- /var/tmp/diff_new_pack.iB5gmu/_old 2020-04-22 20:54:24.187557952 +0200 +++ /var/tmp/diff_new_pack.iB5gmu/_new 2020-04-22 20:54:24.191557959 +0200 @@ -87,8 +87,10 @@ Patch13: %{name}-patch-gdb.patch Patch15: %{name}_enable_snappy_support.patch Patch16: eppic-support-arm64.patch +Patch18: %{name}-stop_read_error_when_intent_is_retry.patch Patch21: %{name}-allow-use-of-sadump-captured-KASLR-kernel.patch -Patch24: %{name}-s390-autodetect-kaslr.patch +Patch23: %{name}-SLE15-SP1-With-Linux-4.19-rc1-up-MAX_PHYSMEM_BITS-to-128TB.patch +Patch24: %{name}-SLE15-SP1-Fix-for-PPC64-kernel-virtual-address-translation-in.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 @@ -275,6 +277,18 @@ %endif +# Compatibility cruft +# there is no %%license prior to SLE12 +%if %{undefined _defaultlicensedir} +%define license %doc +%else +# filesystem before SLE12 SP3 lacks /usr/share/licenses +%if 0%(test ! -d %{_defaultlicensedir} && echo 1) +%define _defaultlicensedir %{_defaultdocdir} +%endif +%endif +# End of compatibility cruft + %prep %setup -q -a 2 -a 4 %patch1 -p1 @@ -285,8 +299,14 @@ %patch10 -p1 %patch11 -p1 %patch13 -p1 +%patch18 -p1 %patch21 -p1 +# Patches for SLE 15 SP1 potentially break support for SLE15 and SLE 12 SP4 +# Don't apply on these (and earlier) versions - see bsc#1148197 +%if 0%{?sle_version} > 120400 && 0%{?sle_version} != 150000 +%patch23 -p1 %patch24 -p1 +%endif %patch25 -p1 %patch26 -p1 %if %{have_snappy} @@ -400,7 +420,8 @@ %defattr(-,root,root) %{_bindir}/crash %{_mandir}/man8/crash.8* -%doc README README.SUSE COPYING3 +%license COPYING3 +%doc README README.SUSE %dir %{_libdir}/crash %dir %{_libdir}/crash/extensions ++++++ crash-SLE15-SP1-Fix-for-PPC64-kernel-virtual-address-translation-in.patch ++++++ >From 28fa7bd09013455b5ddc020dea4706278cda0d65 Mon Sep 17 00:00:00 2001 From: Hari Bathini <[email protected]> Date: Wed, 20 Jun 2018 01:34:22 +0530 Subject: book3s/ppc64: Increase the VA range Upstream: no, adapts the below upstream commit for SLE15 SP1 Git-commit: 28fa7bd09013455b5ddc020dea4706278cda0d65 Fix for PPC64 kernel virtual address translation in Linux 4.17 and later kernels with commit c2b4d8b7417a59b7f9a52d0d8402f5257cbbd398, titled "powerpc/mm/hash64: Increase the VA range", in which the maximum virtual address value has been increased to 4PB. Without the patch, the translation/access of high vmalloc space addresses fails; for example, the "kmem -[sS]" option fails the translation of per-cpu kmem_cache_cpu addresses located in vmalloc space, with the error messages "kmem: invalid kernel virtual address: <address> type: kmem_cache_cpu.freelist" and "kmem: invalid kernel virtual address: <address> type: kmem_cache_cpu.page", and the "vtop" command shows the addresses as "(not mapped)". ([email protected]) [note: apply on 4.12+ for SLE 15 SP1 - incompatible with SLE 15 SP0] --- Index: crash-7.2.8/ppc64.c =================================================================== --- crash-7.2.8.orig/ppc64.c +++ crash-7.2.8/ppc64.c @@ -519,8 +519,9 @@ ppc64_init(int when) if (THIS_KERNEL_VERSION >= LINUX(4,12,0)) { m->l2_index_size = PMD_INDEX_SIZE_L4_64K_4_12; - if (THIS_KERNEL_VERSION >= LINUX(4,17,0)) - m->l3_index_size = PUD_INDEX_SIZE_L4_64K_4_17; + if (THIS_KERNEL_VERSION >= LINUX(4,17,0) || + is_SLE15SP1()) + m->l3_index_size = PUD_INDEX_SIZE_L4_64K_4_17; else m->l3_index_size = PUD_INDEX_SIZE_L4_64K_4_12; m->l4_index_size = PGD_INDEX_SIZE_L4_64K_4_12; ++++++ crash-SLE15-SP1-With-Linux-4.19-rc1-up-MAX_PHYSMEM_BITS-to-128TB.patch ++++++ >From 599a6579aa916df7800f8e889d68e4287e4520dd Mon Sep 17 00:00:00 2001 From: Hari Bathini <[email protected]> Date: Thu, 27 Sep 2018 02:06:49 +0530 Subject: ppc64: increase MAX_PHYSMEM_BITS to 128TB Upstream: no, adapts the below upstream commit for SLE15 SP1 Git-commit: 599a6579aa916df7800f8e889d68e4287e4520dd With Linux 4.19-rc1 commit 7d4340bb92a9df78e6e28152f3dd89d9bd82146b, titled "powerpc/mm: Increase MAX_PHYSMEM_BITS to 128TB with SPARSEMEM_VMEMMAP config", the PPC64 MAX_PHYSMEM_BITS value has been bumped up to 47. The appropriate update has been made in this patch. ([email protected]) [note: apply on 4.12+ for SLE 15 SP1 - incompatible with SLE 15 SP0] --- Index: crash-7.2.8/defs.h =================================================================== --- crash-7.2.8.orig/defs.h +++ crash-7.2.8/defs.h @@ -6896,6 +6896,9 @@ extern struct lkcd_environment *lkcd; #define is_SLES9() \ ((THIS_KERNEL_VERSION == LINUX(2,6,5)) && kt->is_suse_kernel) +#define is_SLE15SP1() \ + ((THIS_KERNEL_VERSION >= LINUX(4,12,0)) && kt->is_suse_kernel) + /* * gdb_interface.c */ Index: crash-7.2.8/ppc64.c =================================================================== --- crash-7.2.8.orig/ppc64.c +++ crash-7.2.8/ppc64.c @@ -244,9 +244,14 @@ static int set_ppc64_max_physmem_bits(vo */ machdep->max_physmem_bits = _MAX_PHYSMEM_BITS_4_20; } else if ((machdep->flags & VMEMMAP) && - ((THIS_KERNEL_VERSION >= LINUX(4,19,0)) || is_RHEL8())) { - /* SPARSEMEM_VMEMMAP & v4.19 kernel or later, or RHEL8 */ - machdep->max_physmem_bits = _MAX_PHYSMEM_BITS_4_19; + ((THIS_KERNEL_VERSION >= LINUX(4,19,0)) || + is_RHEL8() || + is_SLE15SP1())) { + /* + * SPARSEMEM_VMEMMAP & v4.19 kernel or later, + * or RHEL8 or SLE-15-SP1 + */ + machdep->max_physmem_bits = _MAX_PHYSMEM_BITS_4_19; } else if (THIS_KERNEL_VERSION >= LINUX(3,7,0)) machdep->max_physmem_bits = _MAX_PHYSMEM_BITS_3_7; else ++++++ crash-stop_read_error_when_intent_is_retry.patch ++++++ From: David Mair <[email protected]> Date: 2017-05-25 10:27:21 -0600 Subject: Avoid printing a read error for a failed read that can be retried References: bnc#1038839 Upstream: tbd When reading a memory image fails it may not be an error if it is still possible to switch image and retry the read. Fix the error message output to only occur if no retries are intended. --- Index: crash-7.2.8/memory.c =================================================================== --- crash-7.2.8.orig/memory.c +++ crash-7.2.8/memory.c @@ -2320,8 +2320,6 @@ readmem(ulonglong addr, int memtype, voi goto readmem_error; case READ_ERROR: - if (PRINT_ERROR_MESSAGE) - error(INFO, READ_ERRMSG, memtype_string(memtype, 0), addr, type); if ((pc->flags & DEVMEM) && (kt->flags & PRE_KERNEL_INIT) && !(error_handle & NO_DEVMEM_SWITCH) && devmem_is_restricted() && switch_to_proc_kcore()) { @@ -2329,6 +2327,8 @@ readmem(ulonglong addr, int memtype, voi return(readmem(addr, memtype, bufptr, size, type, error_handle)); } + if (PRINT_ERROR_MESSAGE) + error(INFO, READ_ERRMSG, memtype_string(memtype, 0), addr, type); goto readmem_error; case PAGE_EXCLUDED:
