Hello community, here is the log from the commit of package crash for openSUSE:Factory checked in at 2015-06-12 20:31:38 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/crash (Old) and /work/SRC/openSUSE:Factory/.crash.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "crash" Changes: -------- --- /work/SRC/openSUSE:Factory/crash/crash.changes 2015-03-25 21:33:16.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.crash.new/crash.changes 2015-06-12 20:31:45.000000000 +0200 @@ -1,0 +2,327 @@ +Wed May 27 16:29:33 UTC 2015 - [email protected] + +- 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. + ([email protected]) + + - 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. + ([email protected]) + + - 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 + ([email protected]) + + - 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. + ([email protected]) + + - 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. + ([email protected]) + + - 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. + ([email protected]) + + - 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". + ([email protected]) + + - Fix for insecure temporary file usage in _rl_tropen() as reported by + readline library CVE-2014-2524. + ([email protected]) + + - When the gdb-<version>.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. + ([email protected]) + + - 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". + ([email protected]) + + - 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. + ([email protected]) + + - 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. + ([email protected]) + + - 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: <dumpfile>: + not a supported file format". + ([email protected]) + + - 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. + ([email protected]) + + - 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. + ([email protected]) + + - 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. + ([email protected]) + + - 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. + ([email protected], [email protected]) + + - 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". + ([email protected]) + + - Build extension modules that utilize the generic extensions/Makefile + with -g. In addition, build the snap.c extension module with -g. + ([email protected]) + + - 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. + ([email protected]) + + - Fix for a typo in "help foreach", and a fix for a spelling error in + "help input". + ([email protected]) + + - Fix for "and and" and "the the" typos in the README file. + ([email protected]) + + - 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". + ([email protected]) + + - 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. + ([email protected], [email protected]) + + - Speed up the session invocation time of "flattened" format dumpfiles ++++ 130 more lines (skipped) ++++ between /work/SRC/openSUSE:Factory/crash/crash.changes ++++ and /work/SRC/openSUSE:Factory/.crash.new/crash.changes Old: ---- 0001-Prepare-for-the-future-increment-of-Linux-3.x-to-4.x.patch crash-7.1.0.tar.gz New: ---- crash-7.1.1.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ crash.spec ++++++ --- /var/tmp/diff_new_pack.IjC5aD/_old 2015-06-12 20:31:46.000000000 +0200 +++ /var/tmp/diff_new_pack.IjC5aD/_new 2015-06-12 20:31:46.000000000 +0200 @@ -46,7 +46,7 @@ Summary: Crash utility for live systems; netdump, diskdump, LKCD or mcore dumpfiles License: GPL-3.0+ and GFDL-1.2 Group: Development/Tools/Debuggers -Version: 7.1.0 +Version: 7.1.1 Release: 0 Source: %{name}-%{version}.tar.gz Source2: crash_whitepaper-%{whitepaper_version}.tar.bz2 @@ -70,7 +70,6 @@ Patch12: eppic-switch-to-system-lib.patch Patch13: %{name}-patch-gdb.patch Patch15: %{name}_enable_snappy_support.patch -Patch20: 0001-Prepare-for-the-future-increment-of-Linux-3.x-to-4.x.patch Patch90: %{name}-sial-ps-2.6.29.diff BuildRequires: bison BuildRequires: flex @@ -262,7 +261,6 @@ %if %{have_snappy} %patch15 -p1 %endif -%patch20 -p1 ## GDB patches #for f in %{S:XXX} ; do # base=`basename "$f"` ++++++ crash-7.1.0.tar.gz -> crash-7.1.1.tar.gz ++++++ /work/SRC/openSUSE:Factory/crash/crash-7.1.0.tar.gz /work/SRC/openSUSE:Factory/.crash.new/crash-7.1.1.tar.gz differ: char 5, line 1 ++++++ crash-debuginfo-compressed.patch ++++++ --- /var/tmp/diff_new_pack.IjC5aD/_old 2015-06-12 20:31:46.000000000 +0200 +++ /var/tmp/diff_new_pack.IjC5aD/_new 2015-06-12 20:31:46.000000000 +0200 @@ -14,7 +14,7 @@ --- a/symbols.c +++ b/symbols.c -@@ -194,9 +194,9 @@ symtab_init(void) +@@ -199,9 +199,9 @@ symtab_init(void) * Pull a bait-and-switch on st->bfd if we've got a separate * .gnu_debuglink file that matches the CRC. Not done for kerntypes. */ @@ -27,7 +27,7 @@ no_debugging_data(FATAL); } -@@ -258,13 +258,16 @@ check_gnu_debuglink(bfd *bfd) +@@ -263,13 +263,16 @@ check_gnu_debuglink(bfd *bfd) char *contents; int crc_offset; unsigned long crc32; @@ -45,7 +45,7 @@ return FALSE; } -@@ -285,14 +288,14 @@ check_gnu_debuglink(bfd *bfd) +@@ -290,14 +293,14 @@ check_gnu_debuglink(bfd *bfd) contents, crc32); if ((pc->debuginfo_file = (char *) ++++++ crash-sles9-time.patch ++++++ --- /var/tmp/diff_new_pack.IjC5aD/_old 2015-06-12 20:31:46.000000000 +0200 +++ /var/tmp/diff_new_pack.IjC5aD/_new 2015-06-12 20:31:46.000000000 +0200 @@ -16,7 +16,7 @@ --- a/defs.h +++ b/defs.h -@@ -708,6 +708,7 @@ struct kernel_table { +@@ -709,6 +709,7 @@ struct kernel_table { ulong p2m_missing; } pvops_xen; int highest_irq; @@ -24,7 +24,7 @@ #define IKCONFIG_AVAIL 0x1 /* kernel contains ikconfig data */ #define IKCONFIG_LOADED 0x2 /* ikconfig data is currently loaded */ int ikconfig_flags; -@@ -6142,6 +6143,13 @@ extern struct lkcd_environment *lkcd; +@@ -6148,6 +6149,13 @@ extern struct lkcd_environment *lkcd; #endif /* LKCD_COMMON */ @@ -53,7 +53,7 @@ if (symbol_exists("__per_cpu_offset")) { if (LKCD_KERNTYPES()) i = get_cpus_possible(); -@@ -4931,7 +4937,7 @@ get_uptime(char *buf, ulonglong *j64p) +@@ -4941,7 +4947,7 @@ get_uptime(char *buf, ulonglong *j64p) if (symbol_exists("jiffies_64")) { get_symbol_data("jiffies_64", sizeof(ulonglong), &jiffies_64); @@ -62,7 +62,7 @@ wrapped = (jiffies_64 & 0xffffffff00000000ULL); if (wrapped) { wrapped -= 0x100000000ULL; -@@ -5509,6 +5515,7 @@ no_cpu_flags: +@@ -5519,6 +5525,7 @@ no_cpu_flags: if (symbol_exists("p2m_mid_missing")) fprintf(fp, " p2m_mid_missing: %lx\n", kt->pvops_xen.p2m_mid_missing); fprintf(fp, " p2m_missing: %lx\n", kt->pvops_xen.p2m_missing); @@ -72,7 +72,7 @@ /* --- a/task.c +++ b/task.c -@@ -3990,6 +3990,12 @@ start_time_timespec(void) +@@ -4015,6 +4015,12 @@ start_time_timespec(void) default: break; } @@ -85,7 +85,7 @@ tt->flags |= NO_TIMESPEC; -@@ -4021,6 +4027,11 @@ convert_start_time(ulonglong start_time, +@@ -4046,6 +4052,11 @@ convert_start_time(ulonglong start_time, ulong tmp1, tmp2; ulonglong wrapped;
