- Issued:
- 2009-01-20
- Updated:
- 2009-01-20
RHBA-2009:0240 - Bug Fix Advisory
Synopsis
crash bug fix update
Type/Severity
Bug Fix Advisory
Red Hat Insights patch analysis
Identify and remediate systems affected by this advisory.
Topic
Updated crash packages that resolve several issues are now available.
Description
The crash packages are used to investigate live systems and kernel core
dumps created from the netdump, diskdump and kdump facilities.
These updated crash packages provide fixes for the following bugs:
- analyzing an x86 linux kernel core dump (vmcore) using a vmlinux kernel
file very similar to--but not the exact twin of--the vmlinux of the kernel
that dumped core, is an acceptable though non-recommended practice. When
this is done, proper practice calls for adding the location of the
corresponding System.map file to the command line invocation so that the
correct symbol values are used. This fix resolves an issue that occurred
while analyzing a vmcore file in this way, which eventually lead to a
cascade of divide-by-zero SIGFPE exceptions. In these updated packages,
this condition is detected and prevented when examining a vmcore using a
vmlinux that does not exactly correspond to the kernel that crashed and
produced the vmcore.
- the crash utility's "search -u" option, which searches the current
context's user virtual address space for a given value, caused a
segmentation fault when run on a xen-syms hypervisor binary, and gave a
somewhat misleading error message when run on a vmlinux binary on a kernel
thread. Attempting to perform a "search -u" on either of these two types of
binary does not make sense because the xen-syms hypervisor and vmlinux
kernel threads do not have user address space regions. In addition, the
"search -k" option, which searches the kernel virtual address space for a
given value, when run on a xen-syms hypervisor binary, would display a
nonsensical vmlinux-based error message. That option should not be used
with the xen-syms hypervisor, which requires that a starting virtual
address be supplied. With these updated packages, attempting to use crash's
"search" utility in these erroneous ways results in an appropriate error
message being written to the console.
- on Itanium(r) systems, the crash utility's "search -k" option starts its
search at the base of the Itanium(r) virtual memory region containing the
mapped kernel text and static data. However, this region is not necessarily
backed by physical memory. Due to this fact, on Red Hat Enterprise Linux 5
Itanium(r) CONFIG_SPARSEMEM kernels, the "search -k" option caused a
segmentation violation. These updated packages contain a fix which
appropriately sets the start of the Itanium(r) kernel virtual address space
search to the start of kernel text within that region, thus resolving the
issue.
- running the command "crash -i <input-file> <vmlinux> <vmcore>" from the
command line works as expected, but running the same command from inside a
script without a controlling terminal--such as from an init script at
startup--resulted in crash becoming unresponsive (i.e. hanging), and the
following error message being printed: "crash: /dev/tty: No such device or
address". In these updated packages, the crash command no longer assumes
that it is being run with a controlling terminal, and thus no longer hangs
in this situation, which resolves the issue.
- when running the "bt" command on x86 dumpfiles, the backtrace failed to
make the transition from the hard IRQ stack back to the process stack, and
therefore did not display the interrupt exception frame and any kernel
functions leading to the interrupt. In these updated packages, both the
interrupt exception frame and any kernal functions leading up to the
interrupt are displayed.
All users of crash are advised to upgrade to these updated packages, which
resolve these issues.
Solution
Before applying this update, make sure that all previously-released
errata relevant to your system have been applied.
This update is available via Red Hat Network. Details on how to use
the Red Hat Network to apply this update are available at
http://kbase.redhat.com/faq/FAQ_58_10188
Affected Products
- Red Hat Enterprise Linux Server 5 x86_64
- Red Hat Enterprise Linux Server 5 ia64
- Red Hat Enterprise Linux Server 5 i386
- Red Hat Enterprise Linux Workstation 5 x86_64
- Red Hat Enterprise Linux Workstation 5 i386
- Red Hat Enterprise Linux Desktop 5 x86_64
- Red Hat Enterprise Linux Desktop 5 i386
- Red Hat Enterprise Linux for IBM z Systems 5 s390x
- Red Hat Enterprise Linux for Power, big endian 5 ppc
- Red Hat Enterprise Linux Server from RHUI 5 x86_64
- Red Hat Enterprise Linux Server from RHUI 5 i386
Fixes
- BZ - 457371 - Infinite Loop when vmlinux and vmcore Mismatch
- BZ - 457373 - SIGSEGV when Analyse Xen Hypervisor using Search Command
- BZ - 458417 - SIGSEGV when search -k on IA64
- BZ - 458422 - [RFE] Scripting Friendly
- BZ - 462624 - [5.3][crash] bt command does not show interruption frame
CVEs
(none)
References
(none)
Red Hat Enterprise Linux Server 5
SRPM | |
---|---|
crash-4.0-7.2.3.src.rpm | SHA-256: f1e884d60ef55db484d25561d9e82c30b64f1b021f8899123397b7b7ae9217d7 |
x86_64 | |
crash-4.0-7.2.3.x86_64.rpm | SHA-256: b2dd783e798f9ae116785d858e3c933fd27513cd8466ca7db0cf047967f659e3 |
crash-devel-4.0-7.2.3.i386.rpm | SHA-256: 5c1eda3214cd4b10e843f52749c36658d3d82e71601a732b82c830cac7508abc |
crash-devel-4.0-7.2.3.x86_64.rpm | SHA-256: cddbe47a88c8f509d434118e0f3523d5c002d1b65804cd8cf0075f7924577205 |
ia64 | |
crash-4.0-7.2.3.ia64.rpm | SHA-256: 5df397b5feac1554b7eea00aa8724539fb06121307f892276424dc89cf41b7aa |
crash-devel-4.0-7.2.3.ia64.rpm | SHA-256: c39b382a12c33b42e81b0b711a01c0dd88faa5645fe17e19e7b3bb792276a705 |
i386 | |
crash-4.0-7.2.3.i386.rpm | SHA-256: 7224b6e42cd89886da7493f1befb3296e1816b51e95534b470749d0c1d18ca55 |
crash-devel-4.0-7.2.3.i386.rpm | SHA-256: 5c1eda3214cd4b10e843f52749c36658d3d82e71601a732b82c830cac7508abc |
Red Hat Enterprise Linux Workstation 5
SRPM | |
---|---|
crash-4.0-7.2.3.src.rpm | SHA-256: f1e884d60ef55db484d25561d9e82c30b64f1b021f8899123397b7b7ae9217d7 |
x86_64 | |
crash-4.0-7.2.3.x86_64.rpm | SHA-256: b2dd783e798f9ae116785d858e3c933fd27513cd8466ca7db0cf047967f659e3 |
crash-devel-4.0-7.2.3.i386.rpm | SHA-256: 5c1eda3214cd4b10e843f52749c36658d3d82e71601a732b82c830cac7508abc |
crash-devel-4.0-7.2.3.x86_64.rpm | SHA-256: cddbe47a88c8f509d434118e0f3523d5c002d1b65804cd8cf0075f7924577205 |
i386 | |
crash-4.0-7.2.3.i386.rpm | SHA-256: 7224b6e42cd89886da7493f1befb3296e1816b51e95534b470749d0c1d18ca55 |
crash-devel-4.0-7.2.3.i386.rpm | SHA-256: 5c1eda3214cd4b10e843f52749c36658d3d82e71601a732b82c830cac7508abc |
Red Hat Enterprise Linux Desktop 5
SRPM | |
---|---|
crash-4.0-7.2.3.src.rpm | SHA-256: f1e884d60ef55db484d25561d9e82c30b64f1b021f8899123397b7b7ae9217d7 |
x86_64 | |
crash-4.0-7.2.3.x86_64.rpm | SHA-256: b2dd783e798f9ae116785d858e3c933fd27513cd8466ca7db0cf047967f659e3 |
i386 | |
crash-4.0-7.2.3.i386.rpm | SHA-256: 7224b6e42cd89886da7493f1befb3296e1816b51e95534b470749d0c1d18ca55 |
Red Hat Enterprise Linux for IBM z Systems 5
SRPM | |
---|---|
crash-4.0-7.2.3.src.rpm | SHA-256: f1e884d60ef55db484d25561d9e82c30b64f1b021f8899123397b7b7ae9217d7 |
s390x | |
crash-4.0-7.2.3.s390x.rpm | SHA-256: 95fd31a4ed797727fd3b06ba1ec1861746f2c9fd5899f74590595b6627b6c02d |
crash-devel-4.0-7.2.3.s390.rpm | SHA-256: 7a6a848b5fab785ed346fbe9409d5ed347bb05b97a7d5f892a9fe4994ac9b0f8 |
crash-devel-4.0-7.2.3.s390x.rpm | SHA-256: 337ea8a9aaad22f9dfb4f42a99ab9d507b6f6a2a51d981de1cbb2304c274e2e1 |
Red Hat Enterprise Linux for Power, big endian 5
SRPM | |
---|---|
crash-4.0-7.2.3.src.rpm | SHA-256: f1e884d60ef55db484d25561d9e82c30b64f1b021f8899123397b7b7ae9217d7 |
ppc | |
crash-4.0-7.2.3.ppc64.rpm | SHA-256: c804352e23900698031dc274c990b08a06b1435a66067cd17a4056390191fbce |
crash-devel-4.0-7.2.3.ppc64.rpm | SHA-256: fb5d7dcdc24af897823ffedcbd328a27af5384b4025020fd15b2d71ac2f8c187 |
Red Hat Enterprise Linux Server from RHUI 5
SRPM | |
---|---|
crash-4.0-7.2.3.src.rpm | SHA-256: f1e884d60ef55db484d25561d9e82c30b64f1b021f8899123397b7b7ae9217d7 |
x86_64 | |
crash-4.0-7.2.3.x86_64.rpm | SHA-256: b2dd783e798f9ae116785d858e3c933fd27513cd8466ca7db0cf047967f659e3 |
crash-devel-4.0-7.2.3.i386.rpm | SHA-256: 5c1eda3214cd4b10e843f52749c36658d3d82e71601a732b82c830cac7508abc |
crash-devel-4.0-7.2.3.x86_64.rpm | SHA-256: cddbe47a88c8f509d434118e0f3523d5c002d1b65804cd8cf0075f7924577205 |
i386 | |
crash-4.0-7.2.3.i386.rpm | SHA-256: 7224b6e42cd89886da7493f1befb3296e1816b51e95534b470749d0c1d18ca55 |
crash-devel-4.0-7.2.3.i386.rpm | SHA-256: 5c1eda3214cd4b10e843f52749c36658d3d82e71601a732b82c830cac7508abc |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.