[Crash-utility] crash version 4.0-7.6 is available

[Dave Anderson]

- Fix for initialization-time failure if the kernel was built without
  CONFIG_SWAP.  Without the patch, it would fail during initialization
  with the error: "crash: cannot resolve: nr_swapfiles"
  (anderson at redhat.com)

- Fix for the "bt" command when run on x86_64 kernels that contain the 
  x86/x86_64 merger patch.  Without the patch, non-active (blocked)
  tasks do not start with "schedule", and as a result may contain 
  stale frame entries.  (anderson at redhat.com)

- Fix for the usage of an input file of commands redirected during
  runtime via "<", where more than one command in the input file 
  results in a fatal error.  Without the patch, the handling of the
  input file would go into an infinite loop repeatedly running the
  second failed command.  (anderson at redhat.com)

- Clean up causes for warning messages when compiling with gcc 4.3.2.
  (anderson at redhat.com)

- Fix to prevent a segmentation violation during initialization when
  parsing (corrupted) module symbols.  Without the patch, if a kernel 
  module's Elf32_Sym/Elf64_Sym data structure contains a corrupt 
  "st_index" field, the resultant string table access could cause a 
  segmentation violation.  (anderson at redhat.com)

- If an active task experiences a kernel stack overflow, the task's
  thread_info structure located at the very bottom of the stack will
  likely have its "cpu" field corrupted.  Without the patch, any task
  with a corrupt cpu value is not accepted, and the error message 
  "crash: invalid task: <task-address>" is displayed.  With the 
  patch, an active task will be accepted based upon its existence as 
  the current task in a per-cpu runqueue structure, and there will be
  a warning message indicating that the cpu value is corrupt.
  (anderson at redhat.com)

- Modification of the the "files" command when a task has an open file
  referenced by a file descriptor, but the file structure's f_dentry 
  field is NULL.  This is a kernel error condition, but without this 
  patch the "files" command does not display anything for that file 
  descriptor, as if the file has been closed or is not in use.  This 
  patch displays the file descriptor number and the file structure's 
  virtual address.  (anderson at redhat.com)

- Fix for the "bt" command on x86 Xen architectures when the backtrace
  starts on the hard IRQ stack.  Without the patch, the backtrace
  may not properly make the transition back to the process stack
  with the error message "bt: invalid stack address for this task",
  or it may cause a segmentation violation.  (anderson at redhat.com)

Download from: http://people.redhat.com/anderson