All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: vikas.chaudhary@qlogic.com
Cc: jbottomley@parallels.com, linux-scsi@vger.kernel.org,
	lalit.chandivade@qlogic.com, ravi.anand@qlogic.com,
	poornima.vonti@qlogic.com, Sarang Radke <sarang.radke@qlogic.com>
Subject: Re: [PATCH 3/9] qla4xxx: fix call trace on rmmod with ql4xdontresethba=1
Date: Fri, 02 Dec 2011 15:56:46 -0600	[thread overview]
Message-ID: <4ED9499E.5070707@cs.wisc.edu> (raw)
In-Reply-To: <1322808134-21665-4-git-send-email-vikas.chaudhary@qlogic.com>

On 12/02/2011 12:42 AM, vikas.chaudhary@qlogic.com wrote:
>  
>  /**
> + * qla4xxx_is_eh_active:

You need a description of the function above after the colon. And
actually qla4xxx is doing a dash in other places. So you should do:

/**
 * qla4xxx_is_eh_active - check if eh is rinning

And just to make sure, if the host state is in SHOST_CANCEL_RECOVERY the
drivers shutdown code will have cleaned up the command right? It looks
like it, but I was not 100% sure.



> + * @shost: Pointer to SCSI Host struct
> + *
> + * This routine finds that if reset host is called in EH
> + * scenario or from some application like sg_reset
> + **/
> +static int qla4xxx_is_eh_active(struct Scsi_Host *shost)
> +{
> +	if (shost->shost_state == SHOST_RECOVERY)
> +		return 1;
> +	return 0;
> +}
> +
> +/**
>   * qla4xxx_eh_host_reset - kernel callback
>   * @cmd: Pointer to Linux's SCSI command structure
>   *
> @@ -4832,6 +4846,11 @@ static int qla4xxx_eh_host_reset(struct scsi_cmnd *cmd)
>  	if (ql4xdontresethba) {
>  		DEBUG2(printk("scsi%ld: %s: Don't Reset HBA\n",
>  		     ha->host_no, __func__));
> +
> +		/* Clear outstanding srb in queues */
> +		if (qla4xxx_is_eh_active(cmd->device->host))
> +			qla4xxx_abort_active_cmds(ha, DID_ABORT << 16);
> +
>  		return FAILED;
>  	}
>  


  reply	other threads:[~2011-12-02 21:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  6:42 [PATCH 0/9] qla4xxx: Patches for scsi-misc vikas.chaudhary
2011-12-02  6:42 ` [PATCH 1/9] qla4xxx: Perform context resets in case of context failures vikas.chaudhary
2011-12-02  6:42 ` [PATCH 2/9] qla4xxx: Fix CPU lockups when ql4xdontresethba set vikas.chaudhary
2011-12-02  6:42 ` [PATCH 3/9] qla4xxx: fix call trace on rmmod with ql4xdontresethba=1 vikas.chaudhary
2011-12-02 21:56   ` Mike Christie [this message]
2011-12-06 10:46     ` Vikas Chaudhary
2011-12-02  6:42 ` [PATCH 4/9] qla4xxx: Don't recover adapter if device state is FAILED vikas.chaudhary
2011-12-02  6:42 ` [PATCH 5/9] qla4xxx: Wait for disable_acb before doing set_acb vikas.chaudhary
2011-12-02  6:42 ` [PATCH 6/9] qla4xxx: Fix the IDC locking mechanism vikas.chaudhary
2011-12-02  6:42 ` [PATCH 7/9] qla4xxx: Fix qla4xxx_dump_buffer to dump buffer correctly vikas.chaudhary
2011-12-02  6:42 ` [PATCH 8/9] qla4xxx: check for FW alive before calling chip_reset vikas.chaudhary
2011-12-02  6:42 ` [PATCH 9/9] qla4xxx: Update driver version to 5.02.00-k10 vikas.chaudhary
2011-12-06 20:15 ` [PATCH 0/9] qla4xxx: Patches for scsi-misc Mike Christie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ED9499E.5070707@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=jbottomley@parallels.com \
    --cc=lalit.chandivade@qlogic.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=poornima.vonti@qlogic.com \
    --cc=ravi.anand@qlogic.com \
    --cc=sarang.radke@qlogic.com \
    --cc=vikas.chaudhary@qlogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.