Fri May 27 14:00:00 2016 ptesarikAATTsuse.com - eppic-support-arm64.patch: Support for ARM64.
Thu Apr 28 14:00:00 2016 dmairAATTsuse.com - Upgrade of source tarball to 7.1.5 from upstream and fix of crash-sles9-time.patch for the version and refresh of other patches to align with the version. For a detailed changelog of the source tarball see: http://people.redhat.com/anderson/crash.changelog.html includes a fix for bsc#977306. Feature enhancements include: - \"whatis -r\" and \"whatis -m\" commands that allow search for data structure of a specified size and that contains a member of a given type respectively.
Thu Jan 28 13:00:00 2016 vbabkaAATTsuse.com - Upgrade to 7.1.4 from upstream. For a detailed changelog see http://people.redhat.com/anderson/crash.changelog.html
Tue Sep 8 14:00:00 2015 dmairAATTsuse.com - Upgrade of source tarball to 7.1.3 from upstream and refresh of patch series to match. For the changelog of the source tarball see: http://people.redhat.com/anderson/crash.changelog.html Feature enhancements include: - Introduction of the \"dis -f \" option, which disassembles from the target address until the end of the function. - Introduction of the \"dis -s \" option, which displays the filename and line number that is associated with the specified text location, followed by a source code listing if it is available on the host machine. - Added a new \"--src \" command line option for use by the \"dis -s\" option if the kernel source code is not located in the standard location that is compiled into the kernel\'s debuginfo data.
Mon Jul 20 14:00:00 2015 dmairAATTsuse.com - Upgrade to 7.1.2 from upstream. For a detailed changelog see http://people.redhat.com/anderson/crash.changelog.html - Refreshed patch series with some changes required to adjust for git host changes in eppic-switch-to-system-lib.patch
Wed May 27 14:00:00 2015 dmairAATTsuse.com - Upgrade to 7.1.1 from upstream. At the time of writing the only published changelog was supplied by e-mail list and is as follows - Fix for two minor issues with the \"net\" command. Without the patch, the \"net -a\" option appends its correct output with the command\'s \"Usage:\" message; and if either the \"net -x\" or \"net -d\" options are used without also specifying \"-s\" or \"-S\", the error message would indicate \"net: illegal flag: 800000\" or \"net: illegal flag: 1000000\" instead of showing the command\'s \"Usage:\" message. (andersonAATTredhat.com) - If the kernel (live or dumpfile) has the TAINT_LIVEPATCH bit set, or if the Red Hat \"kpatch\" module is installed, the tag \"[LIVEPATCH]\" will be displayed next to the kernel name in the initial system banner and by the \"sys\" command. This new tag replaces the \"[KPATCH]\" tag that was introduced in crash-7.0.7. (andersonAATTredhat.com) - Addressed three Coverity Scan complaints in vmware_vmss.c: 50:leaked_storage: Variable \"fp\" going out of scope leaks the storage it points to. 53:leaked_storage: Variable \"fp\" going out of scope leaks the storage it points to. 256:warning: Use of memory after it is freed (andersonAATTredhat.com) - Remove the LKCD-only \"propeller spinner\" seen when a dumpfile read requires more than 2048 page header accesses. This was put in place because of the non-random-access design of LKCD dumpfiles. Without the patch, the spinner display is intermingled with command output, which complicates the parsing of the output. (watters.samAATTgmail.com) - Fix to support the Linux version increment from 3 to 4. Without the patch, both dumpfile and live sessions fail during initialization, issuing the message \"WARNING: kernel version inconsistency between vmlinux and dumpfile\" or \"WARNING: kernel version inconsistency between vmlinux and live memory\", followed by the nonsensical fatal error message \"crash: incompatible arguments: vmlinux is not SMP -- vmcore is SMP\" or \"crash: incompatible arguments: vmlinux is not SMP -- live system is SMP\". To prevent unexpected kernel version bumps in the future, support has been added for version 5. (andersonAATTredhat.com) - Add support for more than 16TB of physical memory space in the SADUMP dumpfile format. Without the patch, there is a limitation caused by several 32-bit members of dump_header structure, in particular the max_mapnr member, which overflows if the dumpfile contains more than 16TB of physical memory space. The header_version member of the dump_header structure has been increased from 0 to 1 in this extended new format, and the new 64-bit members will be used. (d.hatayamaAATTjp.fujitsu.com) - Fix for command lines that are redirected to a pipe. Without the patch, if an external piped-to command contains a quoted string that includes a \"|\" character, the command fails with the message \"crash: pipe operation failed\". (andersonAATTredhat.com) - Fix for insecure temporary file usage in _rl_tropen() as reported by readline library CVE-2014-2524. (andersonAATTredhat.com) - When the gdb-.patch file has changed and a rebuild is done from within a previously-existing build tree, the \"patch -N\" option is used to ignore patches that have been previously applied; this patch also applies the \"patch -r-\" option to prevent unnecessary .rej files from being created. (andersonAATTredhat.com) - Fix to account for Xen hypervisor\'s \"domain\" structure member name change from \"is_paused_by_controller\" to \"controller_pause_count\". Without the patch, in Xen 4.2.5 and later, the crash session fails during initialization with the error message \'crash: invalid structure member offset: domain_is_paused_by_controller\". (dietmar.hahnAATTts.fujitsu.com) - During initialization, reject useless ARM64 \"(A)\" and \"(a)\" absolute symbols that are below the text region. Without the patch, several recently-introduced absolute symbols have been introduced into the kernel, which will be displayed by \"sym -l\" prior to the first kernel virtual address symbol, and will show up in command output where memory values are translated into kernel symbol references. (andersonAATTredhat.com) - Fix for ARM64 kernels to account for changes in the virtual memory layout introduced in Linux 3.17. The vmalloc region end address, and the vmemmap start and end addresses are now calculated at kernel build time, because they depend upon the size of a struct page. Accordingly, the crash utility needs to calculate those three address values dynamically, after the embedded gdb module has initialized. Without the patch, reads of page structures return invalid data due to incorrect virtual-to-physical translations of memory in the vmemmap range. This in turn causes commands that require page structure contents to fail or show invalid data, such as \"kmem -p\", \"kmem -[sS]\", and the \"kmem -[fF]\" options. (andersonAATTredhat.com) - Fix to support ELF vmcore dumpfiles whose PT_LOAD file offset values of their respective memory segments are not laid out sequentially from low to high in the dumpfile. This has only been seen in ELF dumpfiles created by VMware\'s \"vmss2core -M\" facility. Without the patch, the crash session may fail during initialization, either with the message \"cannot malloc ELF header buffer\", or \"crash: : not a supported file format\". (andersonAATTredhat.com) - Enhancement to the support of VMware .vmss suspended state dumpfiles. There may be holes in the memory address saved for PCI, etc. In such cases, the memory dump is divided into regions. With this patch, up to 3 memory regions are supported. (hfuAATTvmware.com) - Fortified the error handling of task gathering from the pid_hash[] chains during session initialization. If a chain has been corrupted, the patch prevents the sequence from entering an infinite loop, and the error messages associated with corrupt/invalid chains have been updated to report the pid_hash[] index number. (andersonAATTredhat.com) - Implemented a new STRDUPBUF() utility that will duplicate an existing string into a buffer allocated with GETBUF(). As is the case with any buffer allocated with GETBUF(), it is only meant to exist during the life-span of the current command. If it is not explicitly freed via FREEBUF(), then it will be freed automatically prior to the next command. (andersonAATTredhat.com) - Implemented a new fill_struct_member_data() function that gathers a bundle of data that describes a structure member. The function receives a pointer to a struct_member_data structure, in which the caller has initialized the \"structure\" and \"member\" name pointers: struct struct_member_data { char *structure; char *member; long type; long unsigned_type; long length; long offset; long bitpos; long bitsize; }; A gdb \"printm\" command is crafted using those two fields, and the output of the command is used to initialize the remaining six fields. Adapted from Qiao Nuohan\'s \"pstruct\" extension module. (andersonAATTredhat.com, qiaonuohanAATTcn.fujitsu.com) - Implemented a new \"runq -c cpu(s)\" option to display the run queue data of specified cpus. It can be used in conjunction with all runq command options. The cpus must be specified in a comma- and/or dash-separated list; for examples, \"3\", \"1,8,9\", \"1-23\", or \"1,8-15\". (andersonAATTredhat.com) - Build extension modules that utilize the generic extensions/Makefile with -g. In addition, build the snap.c extension module with -g. (rabinvAATTaxis.com) - Several fixes, updates, and enhancements for 32-bit MIPS support: (1) The MIPS general purpose registers in the elf_gregset_t don\'t start at index 0 but at index 6. (2) Adjust for the kernel\'s pt_regs structure changes between kernel versions. For example, fields are inserted into the middle based on build time options, and the amount of padding at the head of the structure was changed relatively recently. To handle this, split the structure definition into two parts and get the offsets of these two parts dynamically. (3) Do not display each parsed kernel symbol during initialization when invoked with \"crash -d8\". (4) Add support for loading raw MIPS ramdump dumpfiles. (5) Add support for compressed kdump dumpfiles. (rabinvAATTaxis.com) - Fix for a typo in \"help foreach\", and a fix for a spelling error in \"help input\". (weijg.fnstAATTcn.fujitsu.com) - Fix for \"and and\" and \"the the\" typos in the README file. (weijg.fnstAATTcn.fujitsu.com) - Fix to address the Xen 4.5.0 hypervisor symbol name change from \"dom0\" to \"hardware_domain\". Without the patch, the crash session fails with the error message \"crash: cannot resolve: dom0\". (dslutzAATTverizon.com) - Fix for a regression in crash-7.1.0 that causes failures when the \"crash -t\" option is run on a live system, and when analyzing remote Linux kernels. Without the patch, \"crash -t\" on a live system fails with the message \"crash: cannot open remote memory source: /dev/mem\", and attempts to analyze a Linux kernel remotely just shows the kernel timestamp and exits immediately. (dslutzAATTverizon.com, andersonAATTredhat.com) - Speed up the session invocation time of \"flattened\" format dumpfiles created by the makedumpfile(8) facility. When sorting the blocks of memory by their intended ELF or compressed kdump file offsets, the patch replaces the bubble-sort method that is currently used with an insertion sort method. (dslutzAATTverizon.com) - Remove the non-existent \"-L\" option from the \"ps\" command\'s mutually- exclusive options error message. (vvsAATTparallels.com) - Fix for the \"irq\", \"mount\", \"kmem -p\" and \"kmem -v\" commands when they are used in an input file. If more than one of any of those four commands are used in an input file, the output of the second and subsequent command instances will not display their respective command headers. (andersonAATTredhat.com) - Implemented a new \"kmem -m\" option that is similar to \"kmem -p\", but it allows the user to specify the page struct members to be displayed. The option takes a comma-separated list of one or more page struct members, which will be displayed following the page structure address. The \"flags\" member will always be expressed in hexadecimal format, and the \"_count\" and \"_mapcount\" members will always be expressed in decimal format. Otherwise, all other members will be displayed in hexadecimal format unless the current output radix is 10 and the member is a signed/unsigned integer. Members that are data structures may be specified by the data structure\'s member name, or expanded to specify a member of that data structure. For example, \"-m lru\" refers to a list_head data structure, in which case both the list_head.next and list_head.prev pointer values will be displayed; if \"-m lru.next\" is specified, just the list_head.next value will be displayed. (atomlinAATTredhat.com, andersonAATTredhat.com) - Support enhancement for the 32-bit MIPS architecture that retrieves the per-cpu registers from the NT_PRSTATUS notes stored in the header of compressed kdump dumpfiles. (rabinvAATTaxis.com) - Fix to remove an invalid warning message on ARM64 if a crash session is invoked with the \"-d\" debug flag. Without the patch, the invalid message is \"WARNING: SPARSEMEM_EX: questionable section values\". (andersonAATTredhat.com) - Remove the leftover \".constructor\" build file in the extensions subdirectory when \"make extensions\" is complete, and update the top-level .gitignore file to ignore post-build extensions subdirectory files. (andersonAATTredhat.com) - Fix for a segmentation violation generated by the \"help -[n|D]\" options on ARM64 compressed kdumps. (andersonAATTredhat.com) - Additional output for the \"help [-D|-n]\" options on ARM64. For ELF kdump vmcores and compressed kdumps, the elf_prstatus structure in each NT_PRSTATUS note will be translated. (andersonAATTredhat.com) - The \"help -r\" option has been extended to dump the ARM64 registers stored in each per-cpu NT_PRSTATUS note in compressed kdump and ELF kdump dumpfiles. (andersonAATTredhat.com) - Fix for the ARM64 page size determination on Linux 4.1 and later kernels. Without the patch, the crash session fails during initialization with the message \"crash: invalid/unsupported page size: 98304\" on kernels with 64K pages. On kernels with 4K pages, the message is \"crash: invalid/unsupported page size: 6144\". In addition, the \"-p \" command line override option had no effect on ARM64; that has been fixed as well. (andersonAATTredhat.com) - Fix for the DATE display in the initial system banner and by the \"sys\" command to account for the Linux 3.17 change that moved the \"timekeeper\" symbol and structure into a containing tk_core structure; the \"shadow_timekeeper\" timekeeper will be used as an alternative. Without the patch, the DATE shows something within a few hours of the Linux epoch, such as \"Wed Dec 31 18:00:00 1969\". (kmcmartinAATTredhat.com) - Fixes for the translation of ARM64 PTEs, as displayed by the \"vm -p\" and \"vtop\" commands. Without the patch, if \"vm -p\" references a swapped-out page on Linux 4.0 and later kernels, the SWAP location may indicate \"(unknown swap location)\", and will show an invalid OFFSET value; on Linux 3.13 and later kernels, running \"vtop\" on a user virtual address incorrectly translates the PTE contents of swapped out pages by showing a PHYSICAL address and FLAGS translation instead of the SWAP device and OFFSET. It is possible that there may be PTE bit translation errors on other kernel versions; the patch addresses the changes in ARM64 PTE bit definitions made in Linux 3.11, 3.13, and 4.0 kernels. (andersonAATTredhat.com) - Enhanced the \"struct.member\" display capability of the \"struct\", \"union\", \"task\", \"list\" and \"tree\" commands. If a specified structure member contains an embedded structure, the output may be restricted to just the embedded structure by expressing the .member argument as \"member.member\". If a specified structure member is an array, the output may be restricted to a single array element by expressing the .member argument as \"member[index]\". Furthermore, these embedded member specifications may extend beyond one level deep, for example, by expressing the member argument as \"member.member.member\", or \"member[index].member\". (Alexandr_TerekhovAATTepam.com, andersonAATTredhat.com) - Fix for any command that passes strings to gdb for evaluation, where the string contains a parentheses-within-parentheses expression along with a \">\" or \">>\" operator inside the outermost set of parentheses. Without the patch, a command such as the following fails like so: crash> p ((1+1) >> 1) p: gdb request failed: p ((1+1) crash> (andersonAATTredhat.com) - Fix for the handling of ARM64 kernel module per-cpu symbols. Without the patch, if the debuginfo data of an ARM64 kernel module that contains a per-cpu section is loaded by \"mod -s \" or \"mod -S\", commands such as \"bt\" or \"sym\" may incorrectly translate the module\'s virtual addresses to symbol names. (Jan.KarlssonAATTsonymobile.com) - 0001-Prepare-for-the-future-increment-of-Linux-3.x-to-4.x.patch: Dropped. Handling kernel 4.0 is now part of the upstream source.
Sun Mar 15 13:00:00 2015 seife+obsAATTb1-systems.com - add patch from upstream to handle kernel 4.0 0001-Prepare-for-the-future-increment-of-Linux-3.x-to-4.x.patch
Fri Feb 6 13:00:00 2015 dmairAATTsuse.com - Upgrade to 7.1.0 from upstream. For a detailed changelog see http://people.redhat.com/anderson/crash.changelog.html - Refreshed patch series with only re-alignment required.
Fri Nov 21 13:00:00 2014 dmairAATTsuse.com - Upgrade to 7.0.9 from upstream, For a detailed changelog see http://people.redhat.com/anderson/crash.changelog.html - Refreshed patch series but no modifications required.
Wed Sep 17 14:00:00 2014 jeffmAATTsuse.com - Upgrade to 7.0.8 from upstream. For a detailed changelog see http://people.redhat.com/anderson/crash.changelog.html - Dropped (now in upstream): - crash-keep-file-orig-with-name-on-select.patch: - As crash-7.0.8/gdb-7.6-ppc64le-support.patch: - crash-gdb-7.6-ppc64_sysv_abi_push_float.patch - crash-gdb-7.6-bound_minimal_symbol.patch - crash-gdb-7.6-add-powerpc64le-linux.patch - crash-gdb-7.6-update-autoconf-2013-04-24.patch - crash-gdb-7.6-ppc_insns_match_pattern.patch - crash-gdb-7.6-floatformat.patch - crash-gdb-7.6-ppc64-ELFv2-trampoline-match.patch - crash-gdb-7.6-update-autoconf-2013-06-10.patch - crash-gdb-7.6-ppc64le.patch
Thu Jul 31 14:00:00 2014 dimstarAATTopensuse.org - Rename rpmlintrc to %{name}-rpmlintrc. Follow the packaging guidelines.
Tue Jul 8 14:00:00 2014 ptesarikAATTsuse.cz - Upgrade to 7.0.7 from upstream. For a detailed changelog see http://people.redhat.com/anderson/crash.changelog.html - crash-x86_64-nested-nmi.patch: Dropped (now in upstream).
Thu Jun 12 14:00:00 2014 dmairAATTsuse.com - crash-keep-file-orig-with-name-on-select.patch Fix the namelist selection for gdb to have background state used to select file to delete for expansion of compressed file (bnc#877367)
Wed Apr 30 14:00:00 2014 ptesarikAATTsuse.cz - crash-x86_64-nested-nmi.patch: Fix NMI backtrace for kernels patched to handle nested NMIs (bnc#874179).
Tue Feb 18 13:00:00 2014 dmairAATTsuse.de - Implementation of 7.0.5 from upstream, including patch refresh Changelog: - Fix for the \"runq -g\" option for kernels that are configured with CONFIG_FAIR_GROUP_SCHED, but not CONFIG_CFS_BANDWIDTH. Without the patch, the command fails with the message \"runq: invalid structure member offset: cfs_rq_throttled\". (vinayakm.listAATTgmail.com) - Add support for Xen PVH guest types introduced in Xen 4.4. Without the patch, running against a Xen 4.4 hypervisor binary would fail during session initialization with the error message \"crash: invalid structure member offset: domain_is_hvm\". In addition, the PVH guest type is being registered internally as an HVM guest type, the debug \"help -X ofs\" command\'s display of the domain_domain_flags offset has been fixed to show it in decimal, and the setting of the internal dc->domain_flags has been fixed to contain all flags set, not just the first one found. (dslutzAATTverizon.com) - Fix for the \"kmem -S\" command on Linux 3.1 and later kernels that are configured with CONFIG_SLUB. Because the the page structure\'s inuse and objects fields used by SLUB were changed from discrete u16 types to bit-fields within an unsigned int, the display of per-node partial slab statistics are incorrect. Without the patch, the TOTAL and ALLOCATED values are incorrectly shown as equal values, and therefore the FREE value is always zero. (andersonAATTredhat.com) - Fix for the \"kmem -S\" command for kernels that are configured with CONFIG_SLUB. Eash per-cpu slab object dump may show incorrect ALLOCATED and FREE values; and as seen on Linux 3.5 and later kernels, the TOTAL value and the number of individual objects dumped may also be incorrect (too small). (andersonAATTredhat.com) - When executing the commands from an input file specified by the \"-i \" command line option, or when accepting input from a file as a set of commands or as a set of command arguments using the \"<\" redirection character, unconditionally cease the operation if CTRL-c is entered. Without the patch, depending upon the command that was running when the SIGINT was received, the operation may continue uninterruptibly until the file contents are consumed. (andersonAATTredhat.com) - Enhanced the \"bt -F\" option such that if \"-F\" is entered twice, and if the stack frame contents reference a slab cache object, both the slab cache name and the stack contents will be displayed within brackets. (andersonAATTredhat.com) - Enhanced the \"rd -S\" option such that if \"-S\" is entered twice, and if the memory contents reference a slab cache object, both the slab cache name and the memory contents will be displayed within brackets. (andersonAATTredhat.com) - Fix for the X86_64 \"bt\" command to prevent an unwarranted message indicating \"WARNING: possibly bogus exception frame\" generated from a blocked kernel thread that was in the process of exec\'ing a user process via the call_usermodehelper() facility. (andersonAATTredhat.com) - Fix for the X86_64 \"bt\" command to more correctly determine the function frame that called into an interrupted function. Without the patch, the first frame just above an IRQ exception frame register dump may show an invalid/stale function. (andersonAATTredhat.com) - Fix for the X86_64 \"bt\" command if a page fault exception was generated by the invalid contents of the RIP register. Without the patch, the exception frame register dump is not displayed above the \"page_fault\" stack frame; and in a related issue, the \"bt -e\" option will not find and display the exception frame. (andersonAATTredhat.com) - When invoking a crash session with a compressed vmlinux file, make the same host-machine/vmlinux endian verification that is done with uncompressed vmlinx files. (andersonAATTredhat.com) - Reduce the number of CTRL-c entries required to unconditionally terminate any manually-entered command from three to one. (andersonAATTredhat.com) - Fix for the X86_64 \"bt\" command if an async page fault exception occurred in a KVM guest running a Linux 2.6.38 or later kernel. Without the patch, the exception frame register dump is not displayed above the \"async_page_fault\" stack frame. (andersonAATTredhat.com)
Fri Jan 24 13:00:00 2014 ptesarikAATTsuse.cz - Enable ppc64le: o crash-patch-gdb.patch: allow applying custom gdb patches o crash-gdb-7.6.series: series file for gdb patches o gdb-7.6-ppc64_sysv_abi_push_float.patch: backported dependency o gdb-7.6-bound_minimal_symbol.patch: dtto o gdb-7.6-add-powerpc64le-linux.patch: dtto o gdb-7.6-update-autoconf-2013-04-24.patch: dtto o gdb-7.6-ppc_insns_match_pattern.patch: dtto o gdb-7.6-floatformat.patch: dtto o gdb-7.6-ppc64-ELFv2-trampoline-match.patch: dtto o gdb-7.6-update-autoconf-2013-06-10.patch: dtto o gdb-7.6-ppc64le.patch: patch used for the gdb package
Fri Jan 24 13:00:00 2014 dmairAATTsuse.com - Implementation of 7.0.4 from upstream and patch refresh. - Fix for the \"ps\" command\'s display of per-task RSS and %MEM values in Linux 2.6.34 and later kernels in which SPLIT_RSS_COUNTING is enabled. Without the patch, the values are only taken from each task\'s mm_struct.rss_stat structure, which may contain stale values because they may not be synchronized with the RSS values stored in each per-thread task_struct.rss_stat structure; this may lead to invalid or slightly low RSS values, and worst-case, the %MEM value may show garbage percentage values. (vinayakm.listAATTgmail.com) - Addressed a few (harmless) Coverity Scan complaints in diskdump.c: 1579:dead_error_line – Execution cannot reach this expression \"\"|\"\" inside statement \"fprintf(fp, \"%sDUMP_DH_COMP...\". 1574:dead_error_line – Execution cannot reach this expression \"\"|\"\" inside statement \"fprintf(fp, \"%sDUMP_HEADER_...\". 1571:dead_error_line – Execution cannot reach this expression \"\"|\"\" inside statement \"fprintf(fp, \"%sDUMP_HEADER_...\". (andersonAATTredhat.com) - Addressed two warnings when compiling diskdump.c on 32-bit architectures when the snappy library is built in: diskdump.c:1046: warning: passing argument 3 of \'snappy_uncompressed_length\' from incompatible pointer type /usr/include/snappy-c.h:120: note: expected ‘size_t *’ but argument is of type ‘ulong *’ diskdump.c:1056: warning: passing argument 4 of ‘snappy_uncompress’ from incompatible pointer type /usr/include/snappy-c.h:103: note: expected ‘size_t *’ but argument is of type ‘ulong *’ (andersonAATTredhat.com) - Created a simpler interface with the internal do_list() function. Currently, if a caller wants to gather the contents of a list into an array, it must do the following: (1) call hq_open() so that the list contents will be verified and saved in the hash queue (2) call do_list() to store the list in the hash queue and return the number of entries in the list (3) allocate a buffer to store the array of entries in the list (4) pass the allocated buffer to retrieve_list() to be populated from the hash queue (5) call hq_close() With this patch, if the passed-in list_data.flags field has a new LIST_ALLOCATE bit set, then do_list() will perform steps (1), (3), (4) and (5) above. The caller can access the allocated array via a new list_data.list_ptr member, and, when done parsing the list, the allocated buffer should be returned via FREEBUF(). The only restriction is that the hash queue cannot be currently in use, or the do_list() call will fail. It should also be noted that there are circumstances where it still makes sense that steps (1), (3), (4) and (5) are performed by the do_list() caller. (andersonAATTredhat.com) - Modified the internal parent_list() function, used by \"ps -p\", to utilize the simpler new do_list() functionality described above. (andersonAATTredhat.com) - Modified the internal dump_vmap_area() function, used by the \"kmem -v\", \"kmem \" and \"search\" commands, to utilize the simpler new do_list() functionality. (andersonAATTredhat.com) - Modified the internal nr_blockdev_pages() function, used by the \"kmem -i\", to utilize the simpler new do_list() functionality. (andersonAATTredhat.com) - Modified the internal get_mount_list() function, used by the \"mount\" and \"files -d\" commands, to utilize the simpler new do_list() functionality. (andersonAATTredhat.com) - Modified the internal get_kmem_cache_list() function, used by the \"kmem -[sS]\", \"kmem \", \"rd -S\" and \"bf -F\" commands, to utilize the simpler new do_list() functionality. (andersonAATTredhat.com) - Modified the internal show_net_devices_v2() and show_net_devices_v3() functions, used by the \"net\" command, to utilize the simpler new do_list() functionality. (andersonAATTredhat.com) - The \"help -r\" option has been extended to dump the X86 and X86_64 registers stored in the NT_PRSTATUS notes in netdump ELF, kdump ELF, and compressed kdump dumpfiles. Without the patch, the option only supports ELF dumpfiles created by the \"virsh dump --memory-only\" facility. (andersonAATTredhat.com) - Modified the \"runq -g\" display to show the CFS task_group and cfs_rq addresses; also the current task is also displayed in its CFS or RT queue with with the notation \"[CURRENT]\" appended to the task data. (Anthony.ChenAATTTeradata.com) - Additional modification to the \"runq -g\" to display the task_group and rt_rq addresses for the RT queues, similar in nature to the CFS queue changes are done by the patch above. In addition, the CFS rb_root and RT prio_array addresses are no longer shown given that they can be determined by looking at the cfs_rq and rt_rq structures whose addresses are now displayed. (andersonAATTredhat.com) - Modified the behavior of the \"mod -t\" option when running against Linux 2.6.18 and earlier kernels such that the hexadecimal value of the module->license_gplok member is always displayed. Without the patch, if a module\'s license_gplok boolean or bitmask value is 0, it would only be displayed if the module was unsigned. (andersonAATTredhat.com, atomlinAATTredhat.com) - Modified the internal dump_tasks_in_task_group_rt_rq() and dump_RT_prio_array() functions, used by the \"runq\" command, to utilize the simpler new do_list() functionality. (andersonAATTredhat.com) - Resurrection of the remote analysis capability for use with the \"xen-crashd\" daemon running on a Xen Dom0 host, which communicates with a paused or shutdown DomU guest kernel. The daemon can be accessed like so: $ crash localhost:5001,/dev/xenmem vmlinux (dslutzAATTverizon.com) - Prevent the X86_64 \"bt\" command from using starting RSP and RIP values taken from the NT_PRSTATUS notes of kdump dumpfiles if the RSP address is not in the task\'s kernel stack, or in any of the relevant per-cpu exception stacks. This can happen when the number of NT_PRSTATUS notes does not match the number of online cpus. Without the patch, the command may generate a segmentation violation, fail with the error message \"bt: cannot determine starting stack pointer\", or fail with an error message indicating that the command \"cannot transition\" from an exception stack to the previous stack. (andersonAATTredhat.com) - Fix for the X86_64 \"bt\" command for displaying the backtraces of active tasks running on the non-crashing cpus in kdump dumpfiles in which the \"crash_nmi_callback\" function frame does not appear in the per-cpu NMI exception stacks. That function frame is normally used as the starting point for the backtraces of those tasks, but if it does not exist, the \"notify_die\" frame will be used instead. Without the patch, the backtraces of the active non-crashing tasks are incorrect or incomplete. (andersonAATTredhat.com) - Increment the X86_64 NR_CPUS maximum value from 5120 to 8192 to be able to account for Linux 3.13-rc1 and later kernels in which CONFIG_MAXSMP has been configured. If that is true, the CONFIG_NR_CPUS value is overridden, and the kernel NR_CPUS value will be set to 8192. This will cause the crash session to fail with the messages \"WARNING: kernel-configured NR_CPUS (8192) greater than compiled-in NR_CPUS (5120)\" and \"crash: recompile crash with larger NR_CPUS\". (andersonAATTredhat.com) - A crash-7.0.3 fix for the proper determination of the kernel NR_CPUS configurable for Linux 3.8 and later kernels introduced a regression in Linux 3.8 and later kernels if: (1) the kernel is configured with CONFIG_SLAB, and (2) the sum of the kernel\'s NR_CPUS and MAX_NUMNODES values exceed the NR_CPUS value compiled into the crash utility. Without the patch, the crash session generates a segmentation fault while it indicates \"please wait: gathering kmem slab cache data\". (andersonAATTredhat.com) - Update for the extensions/trace.c extension module to support the ftrace data structure changes introduced in Linux 3.10 kernels. Without the patch, loading the module with the \"extend\" command fails with the error message \"extend: trace.so: no commands registered: shared object unloaded\". (d.hatayamaAATTjp.fujitsu.com) - Increment the S390 and S390X NR_CPUS maximum value from 64 to 512. (holzheuAATTlinux.vnet.ibm.com) - Implemented support for the redesigned per-slab object bookkeeping that was introduced in Linux 3.13-rc1 for kernels configured with CONFIG_SLAB. In those kernels, the head page structure associated with each slab is overloaded to serve as the (now removed) slab data structure, and the array of kmem_bufctl_t data structures that used to be appended to each slab data structure for object management has been replaced by a new freelist stack mechanism. Without the patch, the crash session would fail during initialization with the error message \"crash: invalid structure member offset: kmem_cache_s_c_num\". It should be noted that this patch has only been tested on 3.13-rc1 kernels, which do not have the modified freelist_idx_t in place as of yet, so the replacement of integer-sized indexes with byte or short sized indexes had not been checked in. Furthermore, if this proposed patch set gets accepted: [RFC][PATCH 0/3] re-shrink \'struct page\' when SLUB is on. https://lkml.org/lkml/2013/12/11/589 then both CONFIG_SLAB and CONFIG_SLUB support in the crash utility will be broken yet again. (andersonAATTredhat.com) - In order to facilitate the building of the crash binary with either or both of the optional LZO or SNAPPY compression libraries, two new Makefile targets have been added: $ make lzo $ make snappy Without the patch, the CFLAGS.extra and LDFLAGS.extra files must be created or modified as described in these changelog entries: http://people.redhat.com/anderson/crash.changelog.html#LZO http://people.redhat.com/anderson/crash.changelog.html#SNAPPY This patch simply does the work automatically. After having done it one time, there is no need to use the targets for subsequent builds. The relevant libraries must pre-exist on the build machine. (andersonAATTredhat.com) - Long overdue update of the README file. (andersonAATTredhat.com)
Tue Dec 10 13:00:00 2013 dvaleevAATTsuse.com - enable ppc64le
Fri Dec 6 13:00:00 2013 ptesarikAATTsuse.cz - crash-compressed-booted-kernel.patch: Fix a bug that may cause removal of the booted kernel\'s vmlinux image (bnc#828260).
Thu Nov 21 13:00:00 2013 dmairAATTsuse.com - Implementation of 7.0.3 from upstream and patch refresh. - Fix for the ARM architecture if the backtrace unwind information cannot be gathered during session initialization. Without the patch, the two unwind-related warning messages indicating \"WARNING: UNWIND: failed to gather unwind_table list\" and \"WARNING: UNWIND: failed to initialize module unwind tables\" are followed by the fatal error message \"crash: cannot hash task_struct entries\". (andersonAATTredhat.com) - Fix for the \"help -[Dn]\" dumpfile information display of the GUID EFI table in the header of SADUMP dumpfiles. Without the patch, only 33 of the 36 bytes in the table are translated. (d.hatayamaAATTjp.fujitsu.com) - Fix for the determination of the kernel NR_CPUS configurable for Linux 3.8 and later kernels that are configured with CONFIG_SLAB. Without the patch, the kernel\'s compiled-in NR_CPUS value was incorrectly calculated to be the sum of the kernel\'s NR_CPUS and MAX_NUMNODES configurables. (andersonAATTredhat.com) - In the next release of makedumpfile, the status field of the dumpfile header of compressed kdumps will show the compression type that was utilized. The \"help -[Dn]\" output has been updated to display that information. (andersonAATTredhat.com) - For kernels configured with CONFIG_SLAB in which an array_cache pointer referenced by a kmem_cache structure is invalid, the individual cache(s) will be marked as invalid. During session initialization, the message \"crash: kmem_cache: : invalid array_cache pointer\" will be displayed, and during runtime, attempts to access the cache(s) will result in a message indicating that the cache is \"[INVALID/CORRPUTED]\". Without the patch, the message \"crash: unable to initialize kmem slab cache subsystem\" is displayed during session initialization, and run-time commands that attempt to access the kmem slab cache subsystem fail with the error message \"kmem cache slab subsystem not available\". (andersonAATTredhat.com) - Fix for the \"kmem -[sS] \" option in Linux 3.6 and later kernels configured with CONFIG_SLAB. Without the patch, the command fails with the message \"kmem: address is not allocated in slab subsystem: . This also causes the \"kmem \" command to (quietly) fail to determine that the address is a slab object. (andersonAATTredhat.com) - Fix for the \"bt\" command if a kernel __init text address is encountered. Without the patch, and depending upon the reallocation of the __init text memory, a bogus framesize may be calculated, or more likely, in a compressed kdump, a warning message indicating \"bt: page excluded: kernel virtual address: type: gdb_readmem_callback\" will be displayed following the frame data. (andersonAATTredhat.com) - Update for determining whether an S390X PTE contains a swap entry in Linux 3.12 and later kernels. (holzheuAATTlinux.vnet.ibm.com) - Resurrected the translation and display of the page.flags bits by the \"kmem -p\" command on Linux 2.6.26 and later kernels whose vmlinux debuginfo data contains either the \"pageflags\" enumerator or the \"pageflag_names\" array of trace_print_flags structures. If they are not available, just the page.flags value is printed in hexadecimal, as has been done since Linux 2.4.9. (andersonAATTredhat.com) - Fix for the \"bt\" command when used with vmcore files that were created with the recently-introduced \"virsh dump --memory-only\", which dumps KVM guests into an ELF vmcore similar to those created by the kdump facility. Without the patch, a faulty backtrace for the panic task may be generated due to the use of incorrect starting RSP/RIP registers; this happens because (unlike kdump) the non-panicking cpus are offlined prior to the dumpfile being created, which in turn leads to the use of the wrong NT_PRSTATUS note. (andersonAATTredhat.com) - Fix for the CPU number display on systems with 255 or more cpus during the initial banner, by the \"set\" command, the \"ps\" command, and by all commands that display the per-task header consisting of the task address, pid, cpu and command name. Without the patch, for cpu 255, the \"sys\" command displays \"NO_PROC_ID\", and the other commands would show a \"-\" for the cpu number; for cpu numbers greater than 255, garbage values would be displayed in the cpu number field. (andersonAATTredhat.com) - Implemented support for compressed kdump header version 6, in which makedumpfile(8) adds new fields in the kdump_sub_header to support large memory systems with pfn values that are larger than 32-bits. Without the patch, if the system contains physical memory located in high memory such that its maximum pfn value is overflows the 32-bit \"max_mapnr\" field in the header, the crash session will fail with the error message \"crash: vmlinux and vmcore do not match!\". (jingbai.maAATThp.com) - Fix for the \"net -s\" command on Linux 3.8 and later kernels. Without the patch, the command fails with the message \"net: invalid structure member offset: inet_opt_daddr\". (andersonAATTredhat.com) - Fix a build failure in a native ARM64 environment due to obsolete LKCD dumpfile headers. (andersonAATTredhat.com) - Implementation of a new \"per-cpu object\" as an argument format that can be passed to the \"p\", \"struct\", \"union\" or \" *\" commands. The format is expressed as either : or as :, where the per-cpu symbol or per-cpu offset must precede a colon, and where the follows the colon. The cpu-identifier may be expressed in any of the following manners: : CPU of the currently selected task. :a[ll] all CPUs. :#[-#][,...] CPU list(s), e.g. \"1,3,5\", \"1-3\", or \"1,3,5-7,10\". Without the patch, per-cpu symbols are only accepted by the \"p\" command, and the data type and the resolved kernel virtual address for each per-cpu instance are displayed shown. With this patch, a colon and a cpu-specifier may be appended to the symbol name, and the the contents of the symbol on each cpu that is specified will be displayed by the \"p\" command. For the \"struct/union/ *\" commands, an argument may be specified using either a per-cpu offset value or per-cpu symbol name followed by a colon and cpu-specifier, and the contents of each structure/union on each specified cpu will be displayed. (ptesarikAATTsuse.cz) Fixed several minor flaws that were detected by a Coverity Scan: tools.c: 992:warning[invalidScanfArgType_int] – %d in format string (no. 1) requires \'int *\' but the argument type is \'unsigned int *\'. memory.c: 7461:error[uninitvar] – Uninitialized variable: page_cache_size filesys.c: 731:error[resourceLeak] – Resource leak: version kernel.c: 5675:error[uninitvar] – Uninitialized variable: action 7799:error[memleakOnRealloc] – Common realloc mistake: \'ikconfig_all\' nulled but not freed upon failure configure.c: 793:error[mismatchAllocDealloc] – Mismatching allocation and deallocation: fp remote.c: 1120:error[resourceLeak] – Resource leak: pipe va_server.c: 316:error[memleak] – Memory leak: disk_hdr va_server_v1.c: 311:error[memleak] – Memory leak: disk_hdr makedumpfile.c: 80:error[memleakOnRealloc] – Common realloc mistake: \'ptr\' nulled but not freed upon failure sadump.c: 231:error[memleakOnRealloc] – Common realloc mistake: \'sdh\' nulled but not freed upon failure extensions/snap.c: 550:error[uninitvar] – Uninitialized variable: prstatus_len 541:error[uninitvar] – Uninitialized variable: l_offset extensions/trace.c: 1477:error[resourceLeak] – Resource leak: file (andersonAATTredhat.com)
Fri Sep 13 14:00:00 2013 ptesarikAATTsuse.com - crash-crosscrash-hint.diff: Removed, because crosscrash isn\'t maintained any longer.
Thu Sep 12 14:00:00 2013 dmairAATTsuse.com - Implementation of v7.0.2 from upstream. o See http://people.redhat.com/anderson/crash.changelog.html for a complete list of changes from 6.1.3. - crash-rl_digit_loop-return.patch - removed - crash-missing-declarations.patch - refreshed - crash-rl_digit_loop-return.patch - refreshed - eppic-switch-to-system-lib.patch - refreshed
Fri May 10 14:00:00 2013 dmairAATTsuse.com - Implementation of v6.1.3 from upstream. crash-display-date-fix.patch - removed/redundant crash-kmem_cache_slab.patch - removed/redundant crash-siginfo.patch - removed/redundant crash-var_length_log_rec.patch - removed/redundant eppic-switch-to-system-lib.patch - Implementation of EPPIC via system library rather than retrieve and include in build. Added eppic constants to spec file without removing the sial constants for now. crash-crosscrash-hint.diff - refreshed crash-make-emacs-default.diff - refreshed crash-sles9-time.patch - refreshed
Wed Feb 27 13:00:00 2013 cooloAATTsuse.com - update license to new format
Mon Feb 4 13:00:00 2013 dmairAATTsuse.com - Re-execution of 150764 by tabrahamAATTsuse.com to re-align patch content, re-number patches for latest spec contents and to remove some incidental content (e.g. whitespace insertion and leftover comments of new lines). Comment from tabraham follows: - added crash-display-date-fix.patch This is a backport of the fix from crash-6.0.9 to fix the date displayed by the initial system banner and by the \"sys\" command for linux kernel 3.6 and later. Without the patch, the date displayed will be that of the UNIX epoch adjusted to local time. - added crash-kmem_cache_slab.patch This is a backport of the fix from crash-6.1.0 for Linux 3.0 and later kernels that have been configured with CONFIG_SLAB and with- out CONFIG_NODES_SHIFT. Without the patch, the warning messages \"crash: nr_node_ids: symbol does not exist\" and \"crash: unable to initialize kmem slab cache subsystem\" are displayed during initialization, and the \"kmem -[sS]\" options fail with the message \"kmem: kmem cache slab subsystem not available\".
Mon Feb 4 13:00:00 2013 dmairAATTsuse.com - crash-compressed-booted-kernel.patch: Fix for \"crash when invoked without arguments fails to analyze the live system\" (bnc#777516).
Fri Jan 25 13:00:00 2013 tabrahamAATTsuse.com - crash-var_length_log_rec.patch: support variable-length record kernel log buffer present in kernel 3.5 and later (bnc#796151).
Sun Jul 29 14:00:00 2012 ajAATTsuse.de - Fix build with glibc 2.16 (struct siginfo -> siginfo_t).
Tue Jul 17 14:00:00 2012 dmairAATTsuse.com - Enabled support for reading dumpfiles compressed by LZO using makedumpfile version 1.4.4 or later.
Fri Jun 1 14:00:00 2012 dmairAATTsuse.com - Update to crash 6.0.7 from upstream and adjust patches to apply without offsets. Upstream changes: o Enhanced the search command to allow the searched-for value to be entered as a crash (expression) or a kernel symbol name. The resultant value of an (expression) or kernel symbol value must fit into in the designated value size if -w or -h are used, and neither variant may be used with the -c option. If found, both the resultant value and the argument input string will be displayed next to the target address(es). o Added a new \"search -t\" option that will restrict the search to the kernel stack pages of all tasks. If one or more matches are found in a task\'s kernel stack, the output is preceded with a task-identifying header. o Fix for the s390x \"bt -[tT]\" options when run on an active task on a live system. Without the patch, the options fail with the message \"bt: invalid/stale stack pointer for this task: 0\". o Fix for s390x \"vm -p\" option, which may show invalid user to physical address translation data if a page is not mapped. Without the patch, a page\'s translation may indicate \" SWAP: (unknown swap location) OFFSET: 0\", or show an incorrect swap offset on an actual swap device. o Added new \"vm -[xd]\" options to be used in conjunction with \"vm -[mv]\", which override the current default output format with hexadecimal or decimal format for just the command instance. Without the patch, it would require changing the default output format with \"hex\" or \"dec\" prior to executing \"vm -[mv]\". The new flags may also be used with \"foreach vm -[mv]\". o Fix for the s390x \"vm -p\" and \"vtop -u \" commands if the page containing the relevant PTE is not mapped. Without the patch, the commands fail with the error message \"vm: read error: kernel virtual address: 0 type: entry\" or \"vtop: read error: kernel virtual address: 0 type: entry\" o Fix for the s390x \"vm -p\" command and \"vtop -u \" commands to properly translate pages that are swapped out into their swap file and offset. Without the patch, the swap file and offset would not be displayed. o Added new \"list -[xd]\" options to be used in conjunction with \"list -s\", which override the current default output format with hexadecimal or decimal format for just the command instance. Without the patch, it would require changing the default output format with \"hex\" or \"dec\" prior to executing \"list -s\". o Added new \"net -[xd]\" options to be used in conjunction with \"net -S\", which override the current default output format with hexadecimal or decimal format for just the command instance. Without the patch, it would require changing the default output format with \"hex\" or \"dec\" prior to executing \"net -S\". The new flags may also be used with \"foreach net -S\". o Added new \"mach -[xd]\" options to be used in conjunction with \"mach -c\", which override the current default output format with hexadecimal or decimal format for just the command instance. Without the patch, it would require changing the default output format with \"hex\" or \"dec\" prior to executing \"mach -c\". o If the value read from the cpu online, present, or possible masks contains a cpu bit value that is outside the architecture\'s maximum NR_CPUS value, print a warning message during invocation. Without the patch, a corrupt vmcore containing a bogus mask value could quietly corrupt heap memory. o Add support to for reading dumpfiles compressed by LZO using makedumpfile version 1.4.4 or later. This feature is disabled by default. To enable this feature, build the crash utility in the following manner: (1) Install the LZO libraries by using the host system\'s package manager or by directly downloading libraries from author\'s website. The packages required are: - lzo - lzo-minilzo - lzo-devel The author\'s website is: http://www.oberhumer.com/opensource/lzo (2) Create a CFLAGS.extra file and an LDFLAGS.extra file in top-level crash sources directory: - enter -DLZO in the CFLAGS.extra file - enter -llzo2 in the LDFLAGS.extra file. (3) Build crash with \"make\" as always.
* Only available as a source option for manual build in this environment o Fix for the included \"trace\" extension module. Without the patch, if the module initialization sequence fails, a double-free in the module may lead to a subsequent malloc() segmentation violation in the crash session. o Incorporated the \"ipcs\" extension module written by Qiao Nuohan as a built-in command. The command displays the kernel\'s usage of the System V shared memory, semaphore and message queue IPC facilities. It differs from the original extension module by fixing a failure scenario if the current task is exiting, and adds a \"-n pid|task\" option, which displays the IPCS facilities with respect to the namespace of a given pid or task. o Fix for a gdb-7.3.1 regression that causes the line number capability to fail with certain ranges of x86 base kernel text addresses. Without the patch, the \"dis -l \" or \"sym \" commands would fail to show line number information for certain ranges of base kernel text addresses. o Added a new \"printm\" command to the embedded gdb module. It is currently only used by the \"pstruct\" extension module, but can be used to dump the type, size, offset, bitpos and bitsize values of an expression. o Added a new \"runq -t\" option that displays the timestamp information of each cpu\'s runqueue, which consists of either the rq.clock, the rq.most_recent_timestamp or rq.timestamp_last_tick value, whichever applies. Following each cpu timestamp is the last_run or timestamp value of the active task on that cpu, whichever applies, along with the task identification. o Fix for an initialization-time warning when running on a live system with the most recent version of the modprobe command, which no longer supports the -l and --type options. The modprobe is used to detect whether the crash.ko memory driver is part of the distribution. Without the patch, a warning message is issued that indicates \"/sbin/modprobe: invalid option -- \'l\'\". If the driver is built into the kernel, the message is harmless. If the driver is not built into kernel, then the crash.ko (/dev/crash) driver would not be selected as the live memory source.
Thu May 17 14:00:00 2012 ptesarikAATTsuse.cz - delete crash-foreach-match-running.patch: upstream
Mon May 14 14:00:00 2012 dmairAATTsuse.com - Update to crash 6.0.6 from upstream o Extend the supported cross-architecture build capability so that it applies to the SIAL extentension module. Without the patch, when building the SIAL module an environment where the overlying crash utility was built with \"make target=ARM\", \"make target=PPC\", or \"make target=X86\", the SIAL extension module would continue to be built for the host architecture o Fixes for memory leaks and possible segmentation violations when unloading SIAL extension module scripts. o Fix for the new \"foreach RU\" task state qualifier. Without the patch, the runnable tasks are not selected. o Fix to disallow multiple task states from being entered using the \"foreach \" qualifier. Without the patch, if multiple states were entered, the last one on the command line would be honored. o Fix for the \"extend\" command to allow the usage of 32-bit PPC extension modules. Without the patch, the command fails with the message: \"extend:
