This is a note to let you know that I've just added the patch titled
megaraid_sas: corrected return of wait_event from abort frame path
to the 3.18-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:
megaraid_sas-corrected-return-of-wait_event-from-abort-frame-path.patch
and it can be found in the queue-3.18 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 170c238701ec38b1829321b17c70671c101bac55 Mon Sep 17 00:00:00 2001
From: "Sumit.Saxena@xxxxxxxxxxxxx" <Sumit.Saxena@xxxxxxxxxxxxx>
Date: Mon, 17 Nov 2014 15:24:23 +0530
Subject: megaraid_sas: corrected return of wait_event from abort frame path
From: "Sumit.Saxena@xxxxxxxxxxxxx" <Sumit.Saxena@xxxxxxxxxxxxx>
commit 170c238701ec38b1829321b17c70671c101bac55 upstream.
Corrected wait_event() call which was waiting for wrong completion
status (0xFF).
Signed-off-by: Sumit Saxena <sumit.saxena@xxxxxxxxxxxxx>
Signed-off-by: Kashyap Desai <kashyap.desai@xxxxxxxxxxxxx>
Reviewed-by: Tomas Henzl <thenzl@xxxxxxxxxx>
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/scsi/megaraid/megaraid_sas_base.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/scsi/megaraid/megaraid_sas_base.c
+++ b/drivers/scsi/megaraid/megaraid_sas_base.c
@@ -1008,7 +1008,7 @@ megasas_issue_blocked_abort_cmd(struct m
cpu_to_le32(upper_32_bits(cmd_to_abort->frame_phys_addr));
cmd->sync_cmd = 1;
- cmd->cmd_status = 0xFF;
+ cmd->cmd_status = ENODATA;
instance->instancet->issue_dcmd(instance, cmd);
Patches currently in stable-queue which might be from Sumit.Saxena@xxxxxxxxxxxxx are
queue-3.18/megaraid_sas-dndinaness-related-bug-fixes.patch
queue-3.18/megaraid_sas-corrected-return-of-wait_event-from-abort-frame-path.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html