Download from: http://people.redhat.com/anderson or https://github.com/crash-utility/crash/releases The github master branch serves as a development branch that will contain all patches that are queued for the next release: $ git clone git://github.com/crash-utility/crash.git Changelog: - Fix for Linux 5.4-rc1 and later kernels that contain commit 688fcbfc06e4fdfbb7e1d5a942a1460fe6379d2d, titled "mm/vmalloc: modify struct vmap_area to reduce its size". Without the patch "kmem -v" will display nothing; other architectures that utilize the vmap_area_list to determine the base of mapped/vmalloc address space will fail. (anderson(a)redhat.com) - Fix for Linux 5.4-rc1 and later kernels that contain commit/merge e0703556644a531e50b5dc61b9f6ea83af5f6604, titled "Merge tag 'modules- for-v5.4' of git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux which introduces symbol namespaces. Without the patch, and depending upon the architecture: (1) the kernel module symbol list will contain garbage entries (2) the session fails during session initialization with a dump of the internal buffer allocation stats followed by the message "crash: cannot allocate any more memory!" (3) the session fails during session initialization with a segmentation violation. (anderson(a)redhat.com) - Fix for the "timer -r" option on Linux 5.4-rc1 and later kernels that contain commit 511885d7061eda3eb1faf3f57dcc936ff75863f1, titled "lib/timerqueue: Rely on rbtree semantics for next timer". Without the patch, the option fails with the following error "timer: invalid structure member offset: timerqueue_head_next". (k-hagio(a)ab.jp.nec.com) - Fix for a "[-Wstringop-truncation]" compiler warning emitted when symbols.c is built in a Fedora Rawhide environment with gcc-9.0.1 or later. (anderson(a)redhat.com) - Fix for the "kmem -n" option on Linux-5.4-rc1 and later kernels that contain commit b6c88d3b9d38f9448e0fcf44847a075ea81d5ca2, titled "drivers/base/memory.c: don't store end_section_nr in memory blocks". Without the patch, the command option fails with the error message "kmem: invalid structure member offset: memory_block_end_section_nr". (msys.mizuma(a)gmail.com) - Fix for Linux 4.19.5 and later 4.19-based x86_64 kernels which are NOT configured with CONFIG_RANDOMIZE_BASE and have backported kernel commit d52888aa2753e3063a9d3a0c9f72f94aa9809c15, titled "x86/mm: Move LDT remap out of KASLR region on 5-level paging", which modified the 4-level and 5-level paging PAGE_OFFSET values. Without this patch, the crash session fails during initialization with the error message "crash: seek error: kernel virtual address: <address> type: "tss_struct ist array". (anderson(a)redhat.com) - Additional fix for the "kmem -n" option on Linux-5.4-rc1 and later kernels that contain commit b6c88d3b9d38f9448e0fcf44847a075ea81d5ca2, titled "drivers/base/memory.c: don't store end_section_nr in memory blocks". The initial fix only addressed the x86_64 architecture; this incremental patch addresses the other architectures. (msys.mizuma(a)gmail.com) - In the unlikely event that the panic task in a dumpfile cannot be determined by the normal means, scan the kernel log buffer for panic keywords, and if found, generate the panic task from the CPU number that is specified following the panic message. (chenqiwu(a)xiaomi.com) - Adjust a crash-7.1.8 patch for support of /proc/kcore as the live memory source in Linux 4.8 and later x86_64 kernels configured with CONFIG_RANDOMIZE_BASE, which randomizes the unity-mapping PAGE_OFFSET value. Since the problem only arises before the determination of the randomized PAGE_OFFSET value, restrict the patch such that it only takes effect during session initialization. (anderson(a)redhat.com) - Add support for extended numbering support in ELF dumpfiles to handle more than PN_XNUM (0xffff) program headers. If the real number of program header table entries is equal to or greater than PN_XNUM, the e_phnum field of the ELF header is set to PN_XNUM, and the actual number is set in the sh_info field of the section header at index 0. (k-hagio(a)ab.jp.nec.com) - Fix for a "warning: large integer implicitly truncated to unsigned type [-Woverflow]" compiler message generated on 32-bit architectures as a result of the "Additional fix for the kmem -n option" patch above. (anderson(a)redhat.com) - Add support for handling openSUSE vmlinux files which will be shipped in .xz compressed format. Without the patch, only gzip and bzip2 formats are supported. (jirislaby(a)gmail.com) - Fix for the determination of the ARM64 page size on Linux 4.4 and earlier kernels that do not have vmcoreinfo data. Without the patch, the crash session fails during initialization with the error message "crash: "cannot determine page size". (chenqiwu(a)xiaomi.com) - Determine the ARM64 kernel's "vabits_actual" value by reading the new TCR_EL1.T1SZ vmcoreinfo entry. (bhsharma(a)redhat.com) - Fix to determine the ARM64 kernel's "vabits_actual" value from the ELF header of a dumpfile created with the "snap.so" extension module. (anderson(a)redhat.com) - Fix two typos in the examples section of the "help bt" display, which mistakenly show "bf -f" and "bf -FF" instead of "bt -f" and "bt -FF". (austindh.kim(a)gmail.com) - Similar to ARM64, the X86_64, PPC64 and S390x architectures will use the exported value of MAX_PHYSMEM_BITS from the vmcoreinfo data as the preferred method if it is available. (anderson(a)redhat.com) - If an S390X kernel crashes before vmcoreinfo initialization, there is no way to extract the KASLR offset for such early dumps. In a new S390X kernel patch, the KASLR offset will be stored in the lowcore memory during early boot and then overwritten after vmcoreinfo is initialized. This patch allows crash to identify the KASLR offset that is stored in the lowcore memory. (zaslonko(a)linux.ibm.com) - Fix for a crash-7.2.7 regression that determined the value of the ARM64 kernel SECTION_SIZE_BITS by reading the in-kernel configuration data if there is no VMCOREINFO data available. In that case, without the patch, a double-free exception may occur. (anderson(a)redhat.com) - Fix for segmentation violation if the gdb_readmem_callback() function gets called from other than a crash command, such as from an epython command from the mypkdump.so extension module. (anderson(a)redhat.com) - Fix for the "dis -s" option when running against kernels that have been configured with CONFIG_RANDOMIZE_BASE=y (KASLR). Without the patch, the command option indicates that the FILE and LINE numbers are "(unknown)", and that "source code is not available". (anderson(a)redhat.com) - Fix for newer Xen hypervisors, which fail during initialization with the error message "crash: cannot resolve init_tss". This is caused by a change in the Xen hypervisor with commit 78884406256, from 4.12.0-rc5-763-g7888440625. In that patch the tss_struct structure was renamed to tss64 and the tss_page structure was introduced, which contains a single tss64. Now tss information is accessible via the symbol "per_cpu__tss_page". (dietmar.hahn(a)ts.fujitsu.com) - When accessing the ARM64 kernel's "crash_notes" array, continue to read the per-cpu NT_PRSTATUS note contents if an invalid note is encountered. Without the patch, if an invalid note is found, all other notes were ignored, and subsequent "bt" attempts on the active tasks would fail. (chenqiwu(a)xiaomi.com, anderson(a)redhat.com) - When accessing the 32-bit ARM kernel's "crash_notes" array, continue to read the per-cpu NT_PRSTATUS note contents if an invalid note is encountered. Without the patch, if an invalid note is found, all other notes were ignored, and subsequent "bt" attempts on the active tasks would fail. (chenqiwu(a)xiaomi.com, anderson(a)redhat.com) - Fix for the "log -a" option. The kernel's sk_buff.len field is a 32-bit unsigned int, but crash was reading its 32-bit value into a 64-bit unsigned long stack variable. All extra bits that pre-existed in the upper 32-bits of the stack variable were passed along as part of a buffer size request; if the upper 32-bit bits were non-zero, then the command would fail with a dump of the internal buffer allocation stats followed by the message "log: cannot allocate any more memory!". (anderson(a)redhat.com) - When determining the ARM64 kernel's "vabits_actual" value by reading the new TCR_EL1.T1SZ vmcoreinfo entry, display its value during session initialization only when invoking crash with "-d1" or larger -d debug value. (anderson(a)redhat.com) - Update copyright to 2020 in crash version output. (anderson(a)redhat.com) - Fix for ARM64 when running against Linux 5.5-rc1 and later kernels that contain commit b6e43c0e3129ffe87e65c85f20fcbdf0eb86fba0, titled "arm64: remove __exception annotations". Without the patch, the ARM64 crash session fails during initialization with the error message "crash: cannot resolve __exception_text_start". (anderson(a)redhat.com) - Fix for support of ELF format kdump vmcores from S390X KASLR kernels. Without the patch, the crash session fails during initialization with the error message "crash: vmlinux and vmcore do not match!". (anderson(a)redhat.com) - Fix for support of S390X standalone dumpfiles and LKCD dumpfiles that were taken from S390X KASLR kernels. (zaslonko(a)linux.ibm.com) - Rework the previous patch for support of S390X standalone dumpfiles and LKCD dumpfiles that were taken from S390X KASLR kernels to avoid calling an s390x-specific function from generic code. (zaslonko(a)linux.ibm.com) - Fix for a gcc-10 compilation error. Without the patch, the build of the crash library fails with a stream of error messages indicating "multiple definition of 'diskdump_flags'" (anderson(a)redhat.com)