scsi: timeout reset timer before command is queued
PATCH 1/1 scsi: timeout reset timer before command is queued
Kernel panic of NULL pointer in scsi_dispatch_cmd during fiber channel scsi disk access. It is because scsi command can time out even before dispatcher queues it to lower level driver, then scsi_times_out error handler could complete the request and free the command memory while scsi_dispatch_cmd still uses the command pointer.
This patch adds new SCSI_EH_RESET_TIMER flag per command to indicate the command hasn't been queued, so scsi_times_out won't complete and free the command. req->special command pointer is also NULLed when the command is freed.
This premature time out is rare, mostly triggered by occasional network delay for fibre channel scsi disk. The patch is verified by instrumenting a testing delay to force scsi_times_out and then monitoring the command pointer integrity.
drivers/scsi/scsi.c +3 -0
@@ -743,6 +743,9 @@ int scsi_dispatch_cmd(struct scsi_cmnd *cmd)*/ scsi_cmd_get_serial (host, cmd); +/* Timeout error handler can start processing cmd now */ + cmd->eh_eflags &= ~SCSI_EH_RESET_TIMER ; +if (unlikely (host->shost_state ==SHOST_DEL )) { cmd->result = (DID_NO_CONNECT <<16 );scsi_done (cmd);
drivers/scsi/scsi_error.c +8 -0
@@ -128,6 +128,14 @@ enum blk_eh_timer_return scsi_times_out(struct request *req)scsi_log_completion (scmd,TIMEOUT_ERROR ); +/* +* Extend timeout if cmd has not been queued yet, otherwise error +* handler could complete request and free the cmd memory while +* the dispatch handler still uses the cmd pointer. +*/ +if (scmd->eh_eflags |SCSI_EH_RESET_TIMER ) +return BLK_EH_RESET_TIMER ; +if (scmd->device->host->transportt->eh_timed_out) rtn = scmd->device->host->transportt->eh_timed_out (scmd);else if (scmd->device->host->hostt->eh_timed_out)
drivers/scsi/scsi_lib.c +0 -0
@@ -492,11 +492,13 @@ void scsi_next_command(struct scsi_cmnd *cmd)
{
struct scsi_device *sdev = cmd->device;
struct request_queue *q = sdev->request_queue;+ struct request *req = cmd->request;
/* need to hold a reference on the device before we let go of the
cmd */
get_device(&sdev->sdev_gendev);
scsi_put_command(cmd);
+ req->special = NULL;
scsi_run_queue(q);
/* ok to remove device now */
@@ -1491,12 +1493,21 @@ static void scsi_request_fn(struct request_queue *q)
/*
* Remove the request from the request list.
*/
+ cmd = req->special;
if (!(blk_queue_tagged(q) && !blk_queue_start_tag(q, req)))
+ {
+ /*
+ * Prevent timeout error handler from processing
+ * the cmd until it is queued in scsi_dispatch_cmd,
+ * otherwise cmd pointer might be freed by error handle
+ */
+ cmd->eh_eflags |= SCSI_EH_RESET_TIMER;
+
blk_start_request(req);
+ }
sdev->device_busy++;
spin_unlock(q->queue_lock);- cmd = req->special;
if (unlikely(cmd == NULL)) {
printk(KERN_CRIT "impossible request in %s.\n"
"please mail a stack trace to "
drivers/scsi/scsi_priv.h +0 -0
@@ -16,6 +16,7 @@ struct scsi_nl_hdr;* Scsi Error Handler Flags */
#define SCSI_EH_CANCEL_CMD 0x0001 /* Cancel this cmd */
+#define SCSI_EH_RESET_TIMER 0x0002 /* Reset timer on the this cmd */
#define SCSI_SENSE_VALID(scmd) \
(((scmd)->sense_buffer[0] & 0x70) == 0x70)Quoted 11 lines · Min Zhang
Kernel panic of NULL pointer in scsi_dispatch_cmd during fiber channelscsi disk access. It is because scsi command can time out even before dispatcher queues it to lower level driver, then
scsi_times_outerror handler could complete the request and free the command memory whilescsi_dispatch_cmdstill uses the command pointer.This patch adds new
SCSI_EH_RESET_TIMERflag per command to indicate the command hasn't been queued, soscsi_times_outwon't complete and free the command.req->specialcommand pointer is also NULLed when the command is freed.
Quoted 7 lines
This premature time out is rare, mostly triggered by occasional network delay for fibre channel scsi disk. The patch is verified by instrumenting a testing delay to force
scsi_times_outand then monitoring the command pointer integrity.Signed-off-by Min Zhang <[email protected]>
OK I stare at the existing code hard and I do not understand why we ask about (blk_queue_tagged(q) && !blk_queue_start_tag(q, req)) twice? And why we let in a failing chance between the blk_start and the dispatch?
I mean why not do the below?
This should also solve Min's problem by not letting any failure between blk_start_request and scsi_dispatch_cmd.
(Only compile tested just to explain the question above)
---
git diff --stat -p -M drivers/scsi/
drivers/scsi/scsi_lib.c | 38 ++++++++++++++++++-------------------- 1 files changed, 18 insertions(+), 20 deletions(-)
drivers/scsi/scsi_lib.c +18 -20
@@ -1487,26 +1487,6 @@ static void scsi_request_fn(struct request_queue *q)continue ; } - -/* -* Remove the request from the request list. -*/ -if (!(blk_queue_tagged (q) && !blk_queue_start_tag (q, req))) -blk_start_request (req); - sdev->device_busy++; - -spin_unlock (q->queue_lock); - cmd = req->special; -if (unlikely (cmd ==NULL )) { -printk (KERN_CRIT "impossible request in %s.\n" -"please mail a stack trace to " -"[email protected]\n" , - __func__); -blk_dump_rq_flags (req,"foo" ); -BUG (); - } -spin_lock (shost->host_lock); -/* * We hit this when the driver is using a host wide * tag map. For device level tag maps the queue_depth check
@@ -1528,6 +1508,24 @@ static void scsi_request_fn(struct request_queue *q)if (!scsi_host_queue_ready (q, shost, sdev)) goto not_ready; +/* +* Remove the request from the request list. +*/ +blk_start_request (req); + sdev->device_busy++; + +spin_unlock (q->queue_lock); + cmd = req->special; +if (unlikely (cmd ==NULL )) { +printk (KERN_CRIT "impossible request in %s.\n" +"please mail a stack trace to " +"[email protected]\n" , + __func__); +blk_dump_rq_flags (req,"foo" ); +BUG (); + } +spin_lock (shost->host_lock); +scsi_target (sdev)->target_busy++; shost->host_busy++;
Quoted 93 lines
drivers/scsi/scsi.c +3
-0@@ -743,6 +743,9 @@ int scsi_dispatch_cmd(struct scsi_cmnd *cmd)*/ scsi_cmd_get_serial (host, cmd); +/* Timeout error handler can start processing cmd now */ + cmd->eh_eflags &= ~SCSI_EH_RESET_TIMER ; +if (unlikely (host->shost_state ==SHOST_DEL )) { cmd->result = (DID_NO_CONNECT <<16 );scsi_done (cmd);drivers/scsi/scsi_error.c +8
-0@@ -128,6 +128,14 @@ enum blk_eh_timer_return scsi_times_out(struct request *req)scsi_log_completion (scmd ,TIMEOUT_ERROR ); +/* +* Extend timeout if cmd has not been queued yet, otherwise error +* handler could complete request and free the cmd memory while +* the dispatch handler still uses the cmd pointer. +*/ +if (scmd->eh_eflags |SCSI_EH_RESET_TIMER ) +return BLK_EH_RESET_TIMER ; +if (scmd->device->host->transportt->eh_timed_out) rtn = scmd->device->host->transportt->eh_timed_out (scmd);else if (scmd->device->host->hostt->eh_timed_out)drivers/scsi/scsi_lib.c +1
-0@@ -492,11 +492,13 @@ void scsi_next_command(struct scsi_cmnd *cmd) {struct scsi_device *sdev = cmd->device;struct request_queue *q = sdev->request_queue; +struct request *req = cmd->request;/* need to hold a reference on the device before we let go of the cmd */
get_device(&sdev->sdev_gendev); scsi_put_command(cmd);drivers/scsi/scsi_lib.c +11
-1+ req->special =NULL ;scsi_run_queue (q);/* ok to remove device now */ @@ -1491,12 +1493,21 @@ static void scsi_request_fn(struct request_queue *q)/* * Remove the request from the request list. */ + cmd = req->special;if (!(blk_queue_tagged (q) && !blk_queue_start_tag (q, req))) + { +/* +* Prevent timeout error handler from processing +* the cmd until it is queued in scsi_dispatch_cmd, +* otherwise cmd pointer might be freed by error handle +*/ + cmd->eh_eflags |=SCSI_EH_RESET_TIMER ; +blk_start_request (req); + } sdev->device_busy++;spin_unlock (q->queue_lock); - cmd = req->special;if (unlikely (cmd ==NULL )) {printk (KERN_CRIT "impossible request in %s.\n" "please mail a stack trace to "drivers/scsi/scsi_priv.h +1
-1@@ -16,6 +16,7 @@ struct scsi_nl_hdr;* Scsi Error Handler Flags */ #define SCSI_EH_CANCEL_CMD 0x0001/* Cancel this cmd */ +#define SCSI_EH_RESET_TIMER 0x0002/* Reset timer on the this cmd */ #define SCSI_SENSE_VALID (scmd) \ (((scmd)->sense_buffer[0] & 0x70) == 0x70) --To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Following is a 2nd version patch further address the timer fired up as early as in blk_queue_start_tag instead of later in scsi_request_fn after blk_queue_start_tag fails.
Boaz, i think your patch will make scsi_request_fn always goto not_ready and skip scsi_dispatch_cmd, because after removing blk_queue_start_tag, subsequent if (blk_queue_tagged(q) && !blk_rq_tagged(req)) is always true. The original blk_queue_start_tag is necessary to set REQ_QUEUE so that blk_rq_tagged check can pass for dispatching. I don't see the other blk_queue_start_tag call.
Also timeout failure can still occur after scsi_request_fn unlock the host_lock and before scsi_dispatch_cmd re-lock it.
---
Kernel panic of NULL pointer in scsi_dispatch_cmd during fiber channel
scsi disk access. It is because scsi command can time out even before dispatcher queues it to lower level driver, then scsi_times_out error handler could complete the request and free the command memory while scsi_dispatch_cmd still uses the command pointer.
This patch adds new SCSI_EH_RESET_TIMER flag per command to indicate the command hasn't been queuecommand, so scsi_times_out won't complete and free the command. req->special command pointer is also NULLed when the command is freed.
This premature time out is rare, mostly triggered by occasional network delay for fibre channel scsi disk. The patch is verified by instrumenting a testing delay to force scsi_times_out and then monitoring the command pointer integrity.
Date: Mon Dec 14 16:41:46 2009 -0800
drivers/scsi/scsi.c +3 -0
@@ -743,6 +743,9 @@ int scsi_dispatch_cmd(struct scsi_cmnd *cmd)*/ scsi_cmd_get_serial (host, cmd); +/* Timeout error handler can start processing cmd now */ + cmd->eh_eflags &= ~SCSI_EH_RESET_TIMER ; +if (unlikely (host->shost_state ==SHOST_DEL )) { cmd->result = (DID_NO_CONNECT <<16 );scsi_done (cmd);
drivers/scsi/scsi_error.c +8 -0
@@ -128,6 +128,14 @@ enum blk_eh_timer_return scsi_times_out(struct request *req)scsi_log_completion (scmd,TIMEOUT_ERROR ); +/* +* Extend timeout if cmd has not been queued yet, otherwise error +* handler could complete request and free the cmd memory while +* the dispatch handler still uses the cmd pointer. +*/ +if (scmd->eh_eflags |SCSI_EH_RESET_TIMER ) +return BLK_EH_RESET_TIMER ; +if (scmd->device->host->transportt->eh_timed_out) rtn = scmd->device->host->transportt->eh_timed_out (scmd);else if (scmd->device->host->hostt->eh_timed_out)
drivers/scsi/scsi_lib.c +0 -0
@@ -492,11 +492,13 @@ void scsi_next_command(struct scsi_cmnd *cmd)
{
struct scsi_device *sdev = cmd->device;
struct request_queue *q = sdev->request_queue;+ struct request *req = cmd->request;
/* need to hold a reference on the device before we let go of the
cmd */
get_device(&sdev->sdev_gendev);
scsi_put_command(cmd);
+ req->special = NULL;
scsi_run_queue(q);
/* ok to remove device now */
@@ -1487,6 +1489,13 @@ static void scsi_request_fn(struct request_queue *q)
continue;
}+ /*
+ * Prevent timeout error handler from processing + * the cmd until it is queued in scsi_dispatch_cmd, + * otherwise cmd pointer might be freed by error handle + */
+ cmd = req->special;
+ cmd->eh_eflags |= SCSI_EH_RESET_TIMER;
/*
* Remove the request from the request list.
@@ -1496,7 +1505,6 @@ static void scsi_request_fn(struct request_queue *q)
sdev->device_busy++;
spin_unlock(q->queue_lock);- cmd = req->special;
if (unlikely(cmd == NULL)) {
printk(KERN_CRIT "impossible request in %s.\n"
"please mail a stack trace to "
drivers/scsi/scsi_priv.h +0 -0
@@ -16,6 +16,7 @@ struct scsi_nl_hdr;* Scsi Error Handler Flags */
#define SCSI_EH_CANCEL_CMD 0x0001 /* Cancel this cmd */
+#define SCSI_EH_RESET_TIMER 0x0002 /* Reset timer on the this cmd */
#define SCSI_SENSE_VALID(scmd) \
(((scmd)->sense_buffer[0] & 0x70) == 0x70)Quoted 179 lines · Boaz Harrosh
Quoted 9 lines · Min Zhang
Kernel panic of NULL pointer in scsi_dispatch_cmd during fiber channel scsi disk access. It is because scsi command can time out even before dispatcher queues it to lower level driver, then scsi_times_out error handler could complete the request and free the command memory while scsi_dispatch_cmd still uses the command pointer.This patch adds new
SCSI_EH_RESET_TIMERflag per command to indicate the command hasn't been queued, soscsi_times_outwon't complete and free the command.req->specialcommand pointer is also NULLed when the command is freed.This premature time out is rare, mostly triggered by occasional network delay for fibre channel scsi disk. The patch is verified by instrumenting a testing delay to force
scsi_times_outand then monitoring the command pointer integrity.Signed-off-by Min Zhang <[email protected]>OK I stare at the existing code hard and I do not understand why we ask about (
blk_queue_tagged(q)&& !blk_queue_start_tag(q, req)) twice? And why we let in a failing chance between theblk_startand the dispatch?I mean why not do the below?
This should also solve Min's problem by not letting any failure between
blk_start_requestandscsi_dispatch_cmd.
(Only compile tested just to explain the question above)
---
git diff --stat -p -Mdrivers/scsi/drivers/scsi/scsi_lib.c | 38 ++++++++++++++++++-------------------- 1 files changed, 18 insertions(+), 20 deletions(-)drivers/scsi/scsi_lib.c +18
-20@@ -1487,26 +1487,6 @@ static void scsi_request_fn(struct request_queue *q)continue ; } - -/* -* Remove the request from the request list. -*/ -if (!(blk_queue_tagged (q) && !blk_queue_start_tag (q, req))) -blk_start_request (req); - sdev->device_busy++; - -spin_unlock (q->queue_lock); - cmd = req->special; -if (unlikely (cmd ==NULL )) { -printk (KERN_CRIT "impossible request in %s.\n" -"please mail a stack trace to " -"[email protected]\n" , - __func__); -blk_dump_rq_flags (req,"foo" ); -BUG (); - } -spin_lock (shost->host_lock); -/* * We hit this when the driver is using a host wide * tag map. For device level tag maps the queue_depth check @@ -1528,6 +1508,24 @@ static void scsi_request_fn(struct request_queue *q)if (!scsi_host_queue_ready (q, shost, sdev)) goto not_ready; +/* +* Remove the request from the request list. +*/ +blk_start_request (req); + sdev->device_busy++; + +spin_unlock (q->queue_lock); + cmd = req->special; +if (unlikely (cmd ==NULL )) { +printk (KERN_CRIT "impossible request in %s.\n" +"please mail a stack trace to " +"[email protected]\n" , + __func__); +blk_dump_rq_flags (req,"foo" ); +BUG (); + } +spin_lock (shost->host_lock); +scsi_target (sdev)->target_busy++; shost->host_busy++;Quoted 95 lines
drivers/scsi/scsi.c +3
-0@@ -743,6 +743,9 @@ int scsi_dispatch_cmd(struct scsi_cmnd *cmd)*/ scsi_cmd_get_serial (host, cmd); +/* Timeout error handler can start processing cmd now */ + cmd->eh_eflags &= ~SCSI_EH_RESET_TIMER ; +if (unlikely (host->shost_state ==SHOST_DEL )) { cmd->result = (DID_NO_CONNECT <<16 );scsi_done (cmd);drivers/scsi/scsi_error.c +8
-0@@ -128,6 +128,14 @@ enum blk_eh_timer_return scsi_times_out(struct request *req)scsi_log_completion (scmd ,TIMEOUT_ERROR ); +/* +* Extend timeout if cmd has not been queued yet, otherwise error +* handler could complete request and free the cmd memory while +* the dispatch handler still uses the cmd pointer. +*/ +if (scmd->eh_eflags |SCSI_EH_RESET_TIMER ) +return BLK_EH_RESET_TIMER ; +if (scmd->device->host->transportt->eh_timed_out) rtn = scmd->device->host->transportt->eh_timed_out (scmd);else if (scmd->device->host->hostt->eh_timed_out)drivers/scsi/scsi_lib.c +1
-0@@ -492,11 +492,13 @@ void scsi_next_command(struct scsi_cmnd *cmd) {struct scsi_device *sdev = cmd->device;struct request_queue *q = sdev->request_queue; +struct request *req = cmd->request;/* need to hold a reference on the device before we let go of the cmd */
get_device(&sdev->sdev_gendev); scsi_put_command(cmd);drivers/scsi/scsi_lib.c +11
-1+ req->special =NULL ;scsi_run_queue (q);/* ok to remove device now */ @@ -1491,12 +1493,21 @@ static void scsi_request_fn(struct request_queue *q)/* * Remove the request from the request list. */ + cmd = req->special;if (!(blk_queue_tagged (q) && !blk_queue_start_tag (q, req))) + { +/* +* Prevent timeout error handler from processing +* the cmd until it is queued in scsi_dispatch_cmd, +* otherwise cmd pointer might be freed by error handle +*/ + cmd->eh_eflags |=SCSI_EH_RESET_TIMER ; +blk_start_request (req); + } sdev->device_busy++;spin_unlock (q->queue_lock); - cmd = req->special;if (unlikely (cmd ==NULL )) {printk (KERN_CRIT "impossible request in %s.\n" "please mail a stack trace to "drivers/scsi/scsi_priv.h +1
-1@@ -16,6 +16,7 @@ struct scsi_nl_hdr;* Scsi Error Handler Flags */ #define SCSI_EH_CANCEL_CMD 0x0001/* Cancel this cmd */ +#define SCSI_EH_RESET_TIMER 0x0002/* Reset timer on the this cmd */ #define SCSI_SENSE_VALID (scmd) \ (((scmd)->sense_buffer[0] & 0x70) == 0x70) --To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 5 lines · Min Zhang
drivers/scsi/scsi.c +0
-0
drivers/scsi/scsi.c int scsi_dispatch_cmd(struct scsi_cmnd *cmd) · line 751
Quoted 9 lines
drivers/scsi/scsi.c +3
-0@@ -743,6 +743,9 @@ int scsi_dispatch_cmd(struct scsi_cmnd *cmd)*/ scsi_cmd_get_serial (host, cmd); +/* Timeout error handler can start processing cmd now */ + cmd->eh_eflags &= ~SCSI_EH_RESET_TIMER ; +if (unlikely (host->shost_state ==SHOST_DEL )) { cmd->result = (DID_NO_CONNECT <<16 );scsi_done (cmd);
Your whitespace seems badly damaged here. Could you fix that?
Quoted 259 lines
drivers/scsi/scsi_error.c +8
-0@@ -128,6 +128,14 @@ enum blk_eh_timer_return scsi_times_out(struct request *req)scsi_log_completion (scmd ,TIMEOUT_ERROR ); +/* +* Extend timeout if cmd has not been queued yet, otherwise error +* handler could complete request and free the cmd memory while +* the dispatch handler still uses the cmd pointer. +*/ +if (scmd->eh_eflags |SCSI_EH_RESET_TIMER ) +return BLK_EH_RESET_TIMER ; +if (scmd->device->host->transportt->eh_timed_out) rtn = scmd->device->host->transportt->eh_timed_out (scmd);else if (scmd->device->host->hostt->eh_timed_out)drivers/scsi/scsi_lib.c +1
-0@@ -492,11 +492,13 @@ void scsi_next_command(struct scsi_cmnd *cmd) {struct scsi_device *sdev = cmd->device;struct request_queue *q = sdev->request_queue; +struct request *req = cmd->request;/* need to hold a reference on the device before we let go of the cmd */
get_device(&sdev->sdev_gendev); scsi_put_command(cmd);drivers/scsi/scsi_lib.c +8
-1+ req->special =NULL ;scsi_run_queue (q);/* ok to remove device now */ @@ -1487,6 +1489,13 @@ static void scsi_request_fn(struct request_queue *q)continue ; } +/* +* Prevent timeout error handler from processing +* the cmd until it is queued in scsi_dispatch_cmd, +* otherwise cmd pointer might be freed by error handle +*/ + cmd = req->special; + cmd->eh_eflags |=SCSI_EH_RESET_TIMER ;/* * Remove the request from the request list. @@ -1496,7 +1505,6 @@ static void scsi_request_fn(struct request_queue *q) sdev->device_busy++;spin_unlock (q->queue_lock); - cmd = req->special;if (unlikely (cmd ==NULL )) {printk (KERN_CRIT "impossible request in %s.\n" "please mail a stack trace to "drivers/scsi/scsi_priv.h +1
-0@@ -16,6 +16,7 @@ struct scsi_nl_hdr;* Scsi Error Handler Flags */ #define SCSI_EH_CANCEL_CMD 0x0001/* Cancel this cmd */ +#define SCSI_EH_RESET_TIMER 0x0002/* Reset timer on the this cmd */ #define SCSI_SENSE_VALID (scmd) \ (((scmd)->sense_buffer[0] & 0x70) == 0x70)Quoted 172 lines · Boaz Harrosh
Quoted 12 lines · Min Zhang
Kernel panic of NULL pointer in scsi_dispatch_cmd during fiberchannel scsi disk access. It is because scsi command can time out even before dispatcher queues it to lower level driver, then
scsi_times_outerror handler could complete the request and free the command memory whilescsi_dispatch_cmdstill uses the command pointer.This patch adds new
SCSI_EH_RESET_TIMERflag per command to indicate the command hasn't been queued, soscsi_times_outwon't complete and free the command.req->specialcommand pointer is also NULLed when the command is freed.Quoted 8 lines
This premature time out is rare, mostly triggered by occasional network delay for fibre channel scsi disk. The patch is verified by instrumenting a testing delay to force
scsi_times_outand then monitoring the command pointer integrity.Signed-off-by Min Zhang <[email protected]>OK I stare at the existing code hard and I do not understand why we ask about (
blk_queue_tagged(q)&& !blk_queue_start_tag(q, req)) twice? And why we let in a failing chance between theblk_startand the dispatch?I mean why not do the below?
This should also solve Min's problem by not letting any failure between
blk_start_requestandscsi_dispatch_cmd.
(Only compile tested just to explain the question above)
---
git diff --stat -p -Mdrivers/scsi/drivers/scsi/scsi_lib.c | 38 ++++++++++++++++++-------------------- 1 files changed, 18 insertions(+), 20 deletions(-)drivers/scsi/scsi_lib.c +17
-19@@ -1487,26 +1487,6 @@ static void scsi_request_fn(struct request_queue *q)continue ; } - -/* -* Remove the request from the request list. -*/ - if (!(blk_queue_tagged(q) && !blk_queue_start_tag(q, req))) -blk_start_request (req); - sdev->device_busy++; - -spin_unlock (q->queue_lock); - cmd = req->special; -if (unlikely (cmd ==NULL )) { -printk (KERN_CRIT "impossible request in %s.\n" -"please mail a stack trace to " -"[email protected]\n" , - __func__); -blk_dump_rq_flags (req,"foo" ); -BUG (); - } -spin_lock (shost->host_lock); -/* * We hit this when the driver is using a host wide * tag map. For device level tag maps the queue_depth check @@ -1528,6 +1508,24 @@ static void scsi_request_fn(struct request_queue *q)if (!scsi_host_queue_ready (q, shost, sdev)) goto not_ready; +/* +* Remove the request from the request list. +*/ +blk_start_request (req); + sdev->device_busy++; + +spin_unlock (q->queue_lock); + cmd = req->special; +if (unlikely (cmd ==NULL )) { +printk (KERN_CRIT "impossible request in %s.\n" +"please mail a stack trace to " +"[email protected]\n" , + __func__); +blk_dump_rq_flags (req,"foo" ); +BUG (); + } +spin_lock (shost->host_lock); +scsi_target (sdev)->target_busy++; shost->host_busy++;Quoted 81 lines
drivers/scsi/scsi.c +2
-0@@ -743,6 +743,9 @@ int scsi_dispatch_cmd(struct scsi_cmnd *cmd)*/ scsi_cmd_get_serial (host, cmd); +/* Timeout error handler can start processing cmd now */ + cmd->eh_eflags &= ~SCSI_EH_RESET_TIMER ; +if (unlikely (host->shost_state ==SHOST_DEL )) { cmd->result = (DID_NO_CONNECT <<16 );scsi_done (cmd);drivers/scsi/scsi_error.c +7
-0@@ -128,6 +128,14 @@ enum blk_eh_timer_return scsi_times_out(struct request *req)scsi_log_completion (scmd ,TIMEOUT_ERROR ); +/* +* Extend timeout if cmd has not been queued yet, otherwise error +* handler could complete request and free the cmd memory while +* the dispatch handler still uses the cmd pointer. +*/ + if (scmd->eh_eflags | SCSI_EH_RESET_TIMER) +return BLK_EH_RESET_TIMER ; +if (scmd->device->host->transportt->eh_timed_out) rtn = scmd->device->host->transportt->eh_timed_out (scmd);else if (scmd->device->host->hostt->eh_timed_out)drivers/scsi/scsi_lib.c +1
-0@@ -492,11 +492,13 @@ void scsi_next_command(struct scsi_cmnd *cmd) {struct scsi_device *sdev = cmd->device;struct request_queue *q = sdev->request_queue; +struct request *req = cmd->request;/* need to hold a reference on the device before we let go of the cmd */
get_device(&sdev->sdev_gendev); scsi_put_command(cmd);drivers/scsi/scsi_lib.c +11
-1+ req->special =NULL ;scsi_run_queue (q);/* ok to remove device now */ @@ -1491,12 +1493,21 @@ static void scsi_request_fn(struct request_queue *q)/* * Remove the request from the request list. */ + cmd = req->special;if (!(blk_queue_tagged (q) && !blk_queue_start_tag (q, req))) + { +/* +* Prevent timeout error handler from processing +* the cmd until it is queued in scsi_dispatch_cmd, +* otherwise cmd pointer might be freed by error handle +*/ + cmd->eh_eflags |=SCSI_EH_RESET_TIMER ; +blk_start_request (req); + } sdev->device_busy++;spin_unlock (q->queue_lock); - cmd = req->special;if (unlikely (cmd ==NULL )) {printk (KERN_CRIT "impossible request in %s.\n" "please mail a stack trace to "drivers/scsi/scsi_priv.h +1
-0@@ -16,6 +16,7 @@ struct scsi_nl_hdr;* Scsi Error Handler Flags */ #define SCSI_EH_CANCEL_CMD 0x0001/* Cancel this cmd */ +#define SCSI_EH_RESET_TIMER 0x0002/* Reset timer on the this cmd */ #define SCSI_SENSE_VALID (scmd) \ (((scmd)->sense_buffer[0] & 0x70) == 0x70)Quoted 7 lines
Quoted 5 lines
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 4 lines
Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step."
Try again, don't know which white space you refer to or how to fix it:
Following is a 2nd version patch further address the timer fired up as early as in blk_queue_start_tag instead of later in scsi_request_fn after blk_queue_start_tag fails.
---
Kernel panic of NULL pointer in scsi_dispatch_cmd during fiber channel
scsi disk access. It is because scsi command can time out even before dispatcher queues it to lower level driver, then scsi_times_out error handler could complete the request and free the command memory while scsi_dispatch_cmd still uses the command pointer.
This patch adds new SCSI_EH_RESET_TIMER flag per command to indicate the command hasn't been queuecommand, so scsi_times_out won't complete and free the command. req->special command pointer is also NULLed when the command is freed.
This premature time out is rare, mostly triggered by occasional network delay for fibre channel scsi disk. The patch is verified by instrumenting a testing delay to force scsi_times_out and then monitoring the command pointer integrity.
Date: Mon Dec 14 16:41:46 2009 -0800
drivers/scsi/scsi.c +3 -0
@@ -743,6 +743,9 @@ int scsi_dispatch_cmd(struct scsi_cmnd *cmd)*/ scsi_cmd_get_serial (host, cmd); +/* Timeout error handler can start processing cmd now */ + cmd->eh_eflags &= ~SCSI_EH_RESET_TIMER ; +if (unlikely (host->shost_state ==SHOST_DEL )) { cmd->result = (DID_NO_CONNECT <<16 );scsi_done (cmd);
drivers/scsi/scsi_error.c +8 -0
@@ -128,6 +128,14 @@ enum blk_eh_timer_return scsi_times_out(struct request *req)scsi_log_completion (scmd,TIMEOUT_ERROR ); +/* +* Extend timeout if cmd has not been queued yet, otherwise error +* handler could complete request and free the cmd memory while +* the dispatch handler still uses the cmd pointer. +*/ +if (scmd->eh_eflags |SCSI_EH_RESET_TIMER ) +return BLK_EH_RESET_TIMER ; +if (scmd->device->host->transportt->eh_timed_out) rtn = scmd->device->host->transportt->eh_timed_out (scmd);else if (scmd->device->host->hostt->eh_timed_out)
drivers/scsi/scsi_lib.c +0 -0
@@ -492,11 +492,13 @@ void scsi_next_command(struct scsi_cmnd *cmd)
{
struct scsi_device *sdev = cmd->device;
struct request_queue *q = sdev->request_queue;+ struct request *req = cmd->request;
/* need to hold a reference on the device before we let go of the
cmd */
get_device(&sdev->sdev_gendev);
scsi_put_command(cmd);
+ req->special = NULL;
scsi_run_queue(q);
/* ok to remove device now */
@@ -1487,6 +1489,13 @@ static void scsi_request_fn(struct request_queue *q)
continue;
}+ /*
+ * Prevent timeout error handler from processing + * the cmd until it is queued in scsi_dispatch_cmd, + * otherwise cmd pointer might be freed by error handle + */
+ cmd = req->special;
+ cmd->eh_eflags |= SCSI_EH_RESET_TIMER;
/*
* Remove the request from the request list.
@@ -1496,7 +1505,6 @@ static void scsi_request_fn(struct request_queue *q)
sdev->device_busy++;
spin_unlock(q->queue_lock);- cmd = req->special;
if (unlikely(cmd == NULL)) {
printk(KERN_CRIT "impossible request in %s.\n"
"please mail a stack trace to "
drivers/scsi/scsi_priv.h +0 -0
@@ -16,6 +16,7 @@ struct scsi_nl_hdr;* Scsi Error Handler Flags */
#define SCSI_EH_CANCEL_CMD 0x0001 /* Cancel this cmd */
+#define SCSI_EH_RESET_TIMER 0x0002 /* Reset timer on the this cmd */
#define SCSI_SENSE_VALID(scmd) \
(((scmd)->sense_buffer[0] & 0x70) == 0x70)drivers/scsi/scsi.c int scsi_dispatch_cmd(struct scsi_cmnd *cmd) · line 751
Quoted 12 lines · Min Zhang
Try again, don't know which white space you refer to or how to fix it:
+++b/drivers/scsi/scsi.cdrivers/scsi/scsi.c +3
-0@@ -743,6 +743,9 @@ int scsi_dispatch_cmd(struct scsi_cmnd *cmd)*/ scsi_cmd_get_serial (host, cmd); +/* Timeout error handler can start processing cmd now */ + cmd->eh_eflags &= ~SCSI_EH_RESET_TIMER ; +if (unlikely (host->shost_state ==SHOST_DEL )) { cmd->result = (DID_NO_CONNECT <<16 );scsi_done (cmd);
Your indent appears to be four spaces. The file uses tabs for indents.
Signature · 4 lines
Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step."
drivers/scsi/scsi_error.c enum blk_eh_timer_return scsi_times_out(struct request *req) · line 137
Quoted 7 lines · Min Zhang
drivers/scsi/scsi_error.c +7
-0+/* +* Extend timeout if cmd has not been queued yet, otherwise error +* handler could complete request and free the cmd memory while +* the dispatch handler still uses the cmd pointer. +*/ +if (scmd->eh_eflags |SCSI_EH_RESET_TIMER ) +return BLK_EH_RESET_TIMER ;
Oh, and what on earth is this? The condition will always be true. I think you meant '&', not '|'.
Signature · 4 lines
Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step."
On 12/15/2009 03:17 AM, Min Zhang wrote:
<snip>
Quoted 8 lines
Boaz, i think your patch will make
scsi_request_fnalways gotonot_readyand skipscsi_dispatch_cmd, because after removingblk_queue_start_tag, subsequent if (blk_queue_tagged(q)&& !blk_rq_tagged(req)) is always true. The originalblk_queue_start_tagis necessary to setREQ_QUEUEso thatblk_rq_taggedcheck can pass for dispatching. I don't see the otherblk_queue_start_tagcall.
You're absolutely right. I got mixed up between blk_queue_start_tag && blk_rq_tagged So I missed the call to blk_queue_start_tag.
Quoted 3 lines
Also timeout failure can still occur after
scsi_request_fnunlock thehost_lockand beforescsi_dispatch_cmdre-lock it.
This was exactly my intention, to do all the things that can fail and the unlocking then relocking before we start the request. And leave no failing possibility and lock released between the start of the request and the dispatching. I think it would be wroth it.
But it's your call
Boaz
Quoted 4 lines · Boaz Harrosh
Quoted 3 lines
Also timeout failure can still occur after
scsi_request_fnunlock thehost_lockand beforescsi_dispatch_cmdre-lock it.
Quoted 8 lines
This was exactly my intention, to do all the things that can fail and the unlocking then relocking before we start the request. And leave no failing possibility and lock released between the start of the request and the dispatching. I think it would be wroth it.
But it's your call
Boaz
How do you leave no failing possibility? As long as there is unlock and then relocking, it is unsafe since timeout could occur right between. Unless you meant hold the lock entirely but your patch didn't show.
e.g. the following scsi_request_fn() cmd could be a corrupt point already. I thought about removing this unlock call, but scsi_dispatch_cmd has this sleep call need to hack around.
/*
* XXX(hch): This is rather suboptimal, scsi_dispatch_cmd will
* take the lock again.
*/
spin_unlock_irq(shost->host_lock);
scsi_init_cmd_errh(cmd);My other wish is to delay the start of timer until command is queued, but that has to change upper layer blk_start_request and might change entire block layer algorithm, too much impact on the other driver that use it.