public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@lst.de>,
	James Bottomley <james.bottomley@hansenpartnership.com>,
	linux-scsi@vger.kernel.org, Bart van Assche <bvanassche@acm.org>
Subject: Re: [PATCH 04/39] scsi: Fixup calling convention for scsi_mode_sense()
Date: Mon, 26 Apr 2021 16:57:58 +0200	[thread overview]
Message-ID: <20210426145758.GE22120@lst.de> (raw)
In-Reply-To: <20210423113944.42672-5-hare@suse.de>

On Fri, Apr 23, 2021 at 01:39:09PM +0200, Hannes Reinecke wrote:
> The description for scsi_mode_sense() claims to return the number
> of valid bytes on success, which is not what the code does.
> Additionally there is no gain in returning the scsi status, as
> everything the callers do is to check against scsi_result_is_good(),
> which is what scsi_mode_sense() does already.
> So change the calling convention to return a standard error code
> on failure, and 0 on success, and adapt the description and all
> callers.
> 
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> ---
>  drivers/scsi/scsi_lib.c           | 10 ++++++----
>  drivers/scsi/scsi_transport_sas.c |  9 ++++-----
>  drivers/scsi/sd.c                 | 12 ++++++------
>  drivers/scsi/sr.c                 |  2 +-
>  4 files changed, 17 insertions(+), 16 deletions(-)
> 
> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
> index d7c0d5a5f263..c532f9390ae3 100644
> --- a/drivers/scsi/scsi_lib.c
> +++ b/drivers/scsi/scsi_lib.c
> @@ -2135,9 +2135,7 @@ EXPORT_SYMBOL_GPL(scsi_mode_select);
>   *	@sshdr: place to put sense data (or NULL if no sense to be collected).
>   *		must be SCSI_SENSE_BUFFERSIZE big.
>   *
> - *	Returns zero if unsuccessful, or the header offset (either 4
> - *	or 8 depending on whether a six or ten byte command was
> - *	issued) if successful.
> + *	Returns zero if successful, or a negative error number on failure
>   */
>  int
>  scsi_mode_sense(struct scsi_device *sdev, int dbd, int modepage,
> @@ -2190,6 +2188,8 @@ scsi_mode_sense(struct scsi_device *sdev, int dbd, int modepage,
>  	 * byte as the problem.  MODE_SENSE commands can return
>  	 * ILLEGAL REQUEST if the code page isn't supported */
>  
> +	if (result < 0)
> +		return result;

The return would be much easier to read if it was just below the call to
scsi_execute_req that assigns result than under the comment
describing the code below.

>  	if (use_10_for_ms && !scsi_status_is_good(result) &&
>  	    driver_byte(result) == DRIVER_SENSE) {
>  		if (scsi_sense_valid(sshdr)) {
> @@ -2228,13 +2228,15 @@ scsi_mode_sense(struct scsi_device *sdev, int dbd, int modepage,
>  			data->block_descriptor_length = buffer[3];
>  		}
>  		data->header_length = header_length;
> +		result = 0;
>  	} else if ((status_byte(result) == CHECK_CONDITION) &&
>  		   scsi_sense_valid(sshdr) &&
>  		   sshdr->sense_key == UNIT_ATTENTION && retry_count) {
>  		retry_count--;
>  		goto retry;
>  	}
> -
> +	if (result > 0)
> +		result = -EIO;

IMHO it would be nice to restructure the end of the function to do
something like:

	if (!scsi_status_is_good(result)) {
		if (status_byte(result) == CHECK_CONDITION &&
		    scsi_sense_valid(sshdr) &&
		    sshdr->sense_key == UNIT_ATTENTION &&
		    retry_count) {
			retry_count--;
			goto retry;
		}
		return -EIO;
	}

	// various data fixups here

	return 0;

  parent reply	other threads:[~2021-04-26 14:58 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23 11:39 [RFC PATCHv2 00/39] SCSI result cleanup, part 2 Hannes Reinecke
2021-04-23 11:39 ` [PATCH 01/39] st: return error code in st_scsi_execute() Hannes Reinecke
2021-04-26  3:19   ` Bart Van Assche
2021-04-26 14:51   ` Christoph Hellwig
2021-04-23 11:39 ` [PATCH 02/39] scsi_ioctl: return error code when blk_rq_map_kern() fails Hannes Reinecke
2021-04-26  3:20   ` Bart Van Assche
2021-04-26 14:51   ` Christoph Hellwig
2021-04-23 11:39 ` [PATCH 03/39] scsi_dh_alua: do not interpret DRIVER_ERROR Hannes Reinecke
2021-04-26 14:54   ` Christoph Hellwig
2021-04-26 15:17     ` Hannes Reinecke
2021-04-23 11:39 ` [PATCH 04/39] scsi: Fixup calling convention for scsi_mode_sense() Hannes Reinecke
2021-04-26  3:21   ` Bart Van Assche
2021-04-26 14:57   ` Christoph Hellwig [this message]
2021-04-23 11:39 ` [PATCH 05/39] scsi: stop using DRIVER_ERROR Hannes Reinecke
2021-04-26  3:26   ` Bart Van Assche
2021-04-26 15:01   ` Christoph Hellwig
2021-04-23 11:39 ` [PATCH 06/39] scsi: introduce scsi_build_sense() Hannes Reinecke
2021-04-26  3:31   ` Bart Van Assche
2021-04-26 15:02   ` Christoph Hellwig
2021-04-23 11:39 ` [PATCH 07/39] scsi: introduce scsi_status_is_check_condition() Hannes Reinecke
2021-04-26  3:34   ` Bart Van Assche
2021-04-26  6:58     ` Hannes Reinecke
2021-04-26 15:02   ` Christoph Hellwig
2021-04-23 11:39 ` [PATCH 08/39] scsi: Kill DRIVER_SENSE Hannes Reinecke
2021-04-26  3:41   ` Bart Van Assche
2021-04-26  7:02     ` Hannes Reinecke
2021-04-26 15:20   ` Christoph Hellwig
2021-04-27  7:15     ` Hannes Reinecke
2021-04-23 11:39 ` [PATCH 09/39] scsi: do not use DRIVER_INVALID Hannes Reinecke
2021-04-26  3:42   ` Bart Van Assche
2021-04-26 15:20   ` Christoph Hellwig
2021-04-23 11:39 ` [PATCH 10/39] scsi_error: use DID_TIME_OUT instead of DRIVER_TIMEOUT Hannes Reinecke
2021-04-26  3:42   ` Bart Van Assche
2021-04-26 15:21   ` Christoph Hellwig
2021-04-26 15:38     ` Hannes Reinecke
2021-04-23 11:39 ` [PATCH 11/39] xen-scsiback: use DID_ERROR instead of DRIVER_ERROR Hannes Reinecke
2021-04-26  3:43   ` Bart Van Assche
2021-04-26 15:22   ` Christoph Hellwig
2021-04-23 11:39 ` [PATCH 12/39] xen-scsifront: compability status handling Hannes Reinecke
2021-04-26  3:44   ` Bart Van Assche
2021-04-26  7:03     ` Hannes Reinecke
2021-04-23 11:39 ` [PATCH 13/39] scsi: Drop the now obsolete driver_byte definitions Hannes Reinecke
2021-04-26  3:46   ` Bart Van Assche
2021-04-26 15:22   ` Christoph Hellwig
2021-04-23 11:39 ` [PATCH 14/39] NCR5380: Fold SCSI message ABORT onto DID_ABORT Hannes Reinecke
2021-04-26 15:23   ` Christoph Hellwig
2021-04-26 15:43     ` Hannes Reinecke
2021-04-23 11:39 ` [PATCH 15/39] scsi: add get_{status,host}_byte() accessor function Hannes Reinecke
2021-04-26  3:47   ` Bart Van Assche
2021-04-26  7:05     ` Hannes Reinecke
2021-04-26 15:23   ` Christoph Hellwig
2021-04-23 11:39 ` [PATCH 16/39] scsi: add translate_msg_byte() Hannes Reinecke
2021-04-26  3:48   ` Bart Van Assche
2021-04-26 15:24   ` Christoph Hellwig
2021-04-26 15:43     ` Hannes Reinecke
2021-04-23 11:39 ` [PATCH 17/39] dc395: use standard macros to set SCSI result Hannes Reinecke
2021-04-26 15:25   ` Christoph Hellwig
2021-04-23 11:39 ` [PATCH 18/39] dc395: translate message bytes Hannes Reinecke
2021-04-26 15:25   ` Christoph Hellwig
2021-04-23 11:39 ` [PATCH 19/39] qlogicfas408: make ql_pcmd() a void function Hannes Reinecke
2021-04-26 15:26   ` Christoph Hellwig
2021-04-26 15:45     ` Hannes Reinecke
2021-04-27  7:36     ` Hannes Reinecke
2021-04-23 11:39 ` [PATCH 20/39] qlogicfas408: whitespace cleanup Hannes Reinecke
2021-04-23 11:39 ` [PATCH 21/39] qlogicfas408: translate message to host byte status Hannes Reinecke
2021-04-23 11:39 ` [PATCH 22/39] nsp32: whitespace cleanup Hannes Reinecke
2021-04-23 11:39 ` [PATCH 23/39] nsp32: do not set message byte Hannes Reinecke
2021-04-23 11:39 ` [PATCH 24/39] wd33c93: translate message byte to host byte Hannes Reinecke
2021-04-24  9:20   ` Finn Thain
2021-04-26  9:07     ` Hannes Reinecke
2021-04-27  4:39       ` Finn Thain
2021-04-27  6:11         ` Hannes Reinecke
2021-04-23 11:39 ` [PATCH 25/39] mesh: translate message to host byte status Hannes Reinecke
2021-04-23 11:39 ` [PATCH 26/39] acornscsi: remove acornscsi_reportstatus() Hannes Reinecke
2021-04-26 15:32   ` Christoph Hellwig
2021-04-23 11:39 ` [PATCH 27/39] acornscsi: translate message byte to host byte Hannes Reinecke
2021-04-23 11:39 ` [PATCH 28/39] aha152x: modify done() to use separate status bytes Hannes Reinecke
2021-04-23 11:39 ` [PATCH 29/39] aha152x: do not set message byte when calling scsi_done() Hannes Reinecke
2021-04-23 11:39 ` [PATCH 30/39] advansys: do not set message byte in SCSI status Hannes Reinecke
2021-04-23 11:39 ` [PATCH 31/39] fas216: translate message to host byte status Hannes Reinecke
2021-04-23 11:39 ` [PATCH 32/39] fas216: Use get_status_byte() to avoid using linux-specific status codes Hannes Reinecke
2021-04-23 11:39 ` [PATCH 33/39] FlashPoint: Use standard SCSI definitions Hannes Reinecke
2021-04-23 11:39 ` [PATCH 34/39] fdomain: drop last argument to fdomain_finish_cmd() Hannes Reinecke
2021-04-23 11:39 ` [PATCH 35/39] fdomain: translate message to host byte status Hannes Reinecke
2021-04-24  9:21   ` Finn Thain
2021-04-23 11:39 ` [PATCH 36/39] scsi: drop message byte helper Hannes Reinecke
2021-04-26  3:48   ` Bart Van Assche
2021-04-23 11:39 ` [PATCH 37/39] scsi: kill message byte Hannes Reinecke
2021-04-26  3:50   ` Bart Van Assche
2021-04-23 11:39 ` [PATCH 38/39] target: use standard SAM status types Hannes Reinecke
2021-04-26  3:51   ` Bart Van Assche
2021-04-23 11:39 ` [PATCH 39/39] scsi: drop obsolete linux-specific SCSI status codes Hannes Reinecke
2021-04-26  3:55   ` Bart Van Assche

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=20210426145758.GE22120@lst.de \
    --to=hch@lst.de \
    --cc=bvanassche@acm.org \
    --cc=hare@suse.de \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox