summaryrefslogtreecommitdiffstats
path: root/drivers/s390/scsi/zfcp_reqlist.h
diff options
context:
space:
mode:
authorSteffen Maier <maier@linux.ibm.com>2019-10-25 18:12:53 +0200
committerMartin K. Petersen <martin.petersen@oracle.com>2019-10-28 22:16:15 -0400
commit100843f176109af94600e500da0428e21030ca7f (patch)
treec3884ac9b15e7c5a67ac88b8b05379bc1b29de55 /drivers/s390/scsi/zfcp_reqlist.h
parente76acc51942649398660ca50655af5afecf29c42 (diff)
downloadlinux-100843f176109af94600e500da0428e21030ca7f.tar.bz2
scsi: zfcp: trace channel log even for FCP command responses
While v2.6.26 commit b75db73159cc ("[SCSI] zfcp: Add qtcb dump to hba debug trace") is right that we don't want to flood the (payload) trace ring buffer, we don't trace successful FCP command responses by default. So we can include the channel log for problem determination with failed responses of any FSF request type. Fixes: b75db73159cc ("[SCSI] zfcp: Add qtcb dump to hba debug trace") Fixes: a54ca0f62f95 ("[SCSI] zfcp: Redesign of the debug tracing for HBA records.") Cc: <stable@vger.kernel.org> #2.6.38+ Link: https://lore.kernel.org/r/e37597b5c4ae123aaa85fd86c23a9f71e994e4a9.1572018132.git.bblock@linux.ibm.com Reviewed-by: Benjamin Block <bblock@linux.ibm.com> Signed-off-by: Steffen Maier <maier@linux.ibm.com> Signed-off-by: Benjamin Block <bblock@linux.ibm.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/s390/scsi/zfcp_reqlist.h')
0 files changed, 0 insertions, 0 deletions