From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: maier@linux.ibm.com, bblock@linux.ibm.com,
martin.petersen@oracle.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] scsi: zfcp: trace channel log even for FCP command responses" failed to apply to 4.19-stable tree
Date: Sun, 15 Dec 2019 11:24:58 -0500 [thread overview]
Message-ID: <20191215162457.GC18043@sasha-vm> (raw)
In-Reply-To: <157633580122434@kroah.com>
On Sat, Dec 14, 2019 at 04:03:21PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.19-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 100843f176109af94600e500da0428e21030ca7f Mon Sep 17 00:00:00 2001
>From: Steffen Maier <maier@linux.ibm.com>
>Date: Fri, 25 Oct 2019 18:12:53 +0200
>Subject: [PATCH] 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>
Conflicts due to:
f9eca0227600 ("scsi: zfcp: drop duplicate fsf_command from zfcp_fsf_req which is also in QTCB header")
I've adjusted it to address the missing commit and queued it for
4.19-4.4.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-12-15 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 15:03 FAILED: patch "[PATCH] scsi: zfcp: trace channel log even for FCP command responses" failed to apply to 4.19-stable tree gregkh
2019-12-15 16:24 ` Sasha Levin [this message]
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=20191215162457.GC18043@sasha-vm \
--to=sashal@kernel.org \
--cc=bblock@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=maier@linux.ibm.com \
--cc=martin.petersen@oracle.com \
--cc=stable@vger.kernel.org \
/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