This is a note to let you know that I've just added the patch titled

    target: Allow PERSISTENT RESERVE IN for non-reservation holder

to the 3.2-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     target-allow-persistent-reserve-in-for-non-reservation-holder.patch
and it can be found in the queue-3.2 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From 6816966a8418b980481b4dced7eddd1796b145e8 Mon Sep 17 00:00:00 2001
From: Marco Sanvido <[email protected]>
Date: Tue, 3 Jan 2012 17:12:58 -0800
Subject: target: Allow PERSISTENT RESERVE IN for non-reservation holder

From: Marco Sanvido <[email protected]>

commit 6816966a8418b980481b4dced7eddd1796b145e8 upstream.

Initiators that aren't the active reservation holder should be able to
do a PERSISTENT RESERVE IN command in all cases, so add it to the list
of allowed CDBs in core_scsi3_pr_seq_non_holder().

Signed-off-by: Marco Sanvido <[email protected]>
Signed-off-by: Roland Dreier <[email protected]>
Signed-off-by: Nicholas Bellinger <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 drivers/target/target_core_pr.c |    1 +
 1 file changed, 1 insertion(+)

--- a/drivers/target/target_core_pr.c
+++ b/drivers/target/target_core_pr.c
@@ -481,6 +481,7 @@ static int core_scsi3_pr_seq_non_holder(
        case READ_MEDIA_SERIAL_NUMBER:
        case REPORT_LUNS:
        case REQUEST_SENSE:
+       case PERSISTENT_RESERVE_IN:
                ret = 0; /*/ Allowed CDBs */
                break;
        default:


Patches currently in stable-queue which might be from [email protected] are

queue-3.2/target-allow-persistent-reserve-in-for-non-reservation-holder.patch
queue-3.2/target-use-correct-preempted-registration-sense-code.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to