Frantisek,

I failed to find the upstream commit 224cb3e981f1b2f9f93dbd49eaef505d17d894c2 as https://bugzilla.redhat.com/show_bug.cgi?id=636771#c36 mentioned in 2.6.32-71.18.1.el6.

static void deactivate_path(struct work_struct *work) is missing.

OK.
This patch just revert 224cb3e981f1b2f9f93dbd49eaef505d17d894c2.

Code reviewed. kernel 2.6.32-71.18.1.el6 has reverted the commit.

Set as Sanity Only.

(In reply to comment #9)
> OK.
> This patch just revert 224cb3e981f1b2f9f93dbd49eaef505d17d894c2.
> 
> Code reviewed. kernel 2.6.32-71.18.1.el6 has reverted the commit.
> 
> Set as Sanity Only.

You may have only done "Sanity Only" but FYI: Barry Donahue and I have done exhaustive testing (using NetAPp's test scripts) on NetApp storage in westford.

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 therefore 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-2011-0283.html

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
A Red Hat Enterprise Linux 6.0 host (with root on a local disk) with dm-multipath configured on multiple LUNs (Logical Unit Number) hit kernel panic (at scsi_error_handler) with target controller faults during an I/O operation on the dm-multipath devices. This was caused by multipath using the blk_abort_queue() function to allow lower latency path deactivation. The call to blk_abort_queue proved to be unsafe due to a race (between blk_abort_queue and scsi_request_fn). With this update, the race has been resolved and kernel panic no longer occurs on Red Hat Enterprise Linux 6.0 hosts.

*** Bug 692670 has been marked as a duplicate of this bug. ***