Bug 166363 - cciss disk dump hangs if module is ever unloaded/reloaded
cciss disk dump hangs if module is ever unloaded/reloaded
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
3.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tom Coughlan
Brian Brock
:
Depends On:
Blocks: 168424
  Show dependency treegraph
 
Reported: 2005-08-19 15:32 EDT by Tom Coughlan
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version: RHSA-2006-0144
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-03-15 11:26:07 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
the patch (1.88 KB, patch)
2005-08-19 15:32 EDT, Tom Coughlan
no flags Details | Diff


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2006:0144 qe-ready SHIPPED_LIVE Moderate: Updated kernel packages available for Red Hat Enterprise Linux 3 Update 7 2006-03-15 00:00:00 EST

  None (edit)
Description Tom Coughlan 2005-08-19 15:32:46 EDT
While debugging the last cciss disk dump problem I experienced a new problem:

service diskdump start
rmmod cciss
insmod cciss
echo c > /proc/sysrq-trigger
The systems gets to "start dumping" and hangs, with no dump created.

The pointers that are set up in diskdump/block_dump are no longer
valid when cciss is unloaded and then reloaded. The solution is to prevent the
cciss driver from being unloaded if it is being used by disk dump. This is
already done correctly in scsi_dump.

I tested this patch (as did HP). I confirmed the cciss usage count is
incremented when diskdump is started/stopped. The cciss module can not be
unloaded while the diskdump service is active on the cciss device. Dumps work as
expected.

This code is similar to what is in scsi_dump.c. An ACK from people familiar with
that code would be particularly helpful.

It would be reasonable to put this is U6, since the risk is low, and it is a fix
for functionality committed in U6. If it does not make it, then we will have to
release note the problem, and fix it in U7.
Comment 1 Tom Coughlan 2005-08-19 15:32:47 EDT
Created attachment 117924 [details]
the patch
Comment 4 Ernie Petrides 2005-09-12 23:27:03 EDT
A fix for this problem has just been committed to the RHEL3 U7
patch pool this evening (in kernel version 2.4.21-37.1.EL).
Comment 7 Red Hat Bugzilla 2006-03-15 11:26:07 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2006-0144.html

Note You need to log in before you can comment on or make changes to this bug.