On 08/08/2014 01:50 PM, Yoshihiro YUNOMAE wrote:
If sense_flags and fixed_valid are zero, the kernel does not need to
output a printk message. So, if those conditions are met, it just returns.

Signed-off-by: Yoshihiro YUNOMAE <[email protected]>
Cc: Hannes Reinecke <[email protected]>
Cc: Doug Gilbert <[email protected]>
Cc: Martin K. Petersen <[email protected]>
Cc: Christoph Hellwig <[email protected]>
Cc: "James E.J. Bottomley" <[email protected]>
Cc: Hidehiro Kawai <[email protected]>
Cc: Masami Hiramatsu <[email protected]>
---
  drivers/scsi/constants.c |    3 +++
  1 file changed, 3 insertions(+)

diff --git a/drivers/scsi/constants.c b/drivers/scsi/constants.c
index a0e8159..9c38b8d 100644
--- a/drivers/scsi/constants.c
+++ b/drivers/scsi/constants.c
@@ -1438,6 +1438,9 @@ scsi_decode_sense_extras(struct scsi_device *sdev, const 
char *name,
                        sense_flags |= ucp[3] & 0xe0;
        }

+       if (!sense_flags && !fixed_valid)
+               return;
+
        res = 0;
        memset(buff, 0, sizeof(buff));
        blen = sizeof(buff) - 1;

--
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

scsi_decode_sense_extras() is utterly weird, as it only decodes tape-specific sense extras. Seeing that 'st' and 'osst' already contains code to handle those cases we should remove this function altogether, as it doesn't serve any purpose.

Has been removed with my next scsi logging update, so this patch is not applicable anymore.

Cheers,

Hannes
--
Dr. Hannes Reinecke                   zSeries & Storage
[email protected]                          +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to