diff options
author | Benjamin Block <bblock@linux.ibm.com> | 2019-07-02 23:02:01 +0200 |
---|---|---|
committer | Martin K. Petersen <martin.petersen@oracle.com> | 2019-07-11 21:04:22 -0400 |
commit | 106d45f350c7cac876844dc685845cba4ffdb70b (patch) | |
tree | 6f68cf4e5780c123d2b51f3513fb822e21045886 /kernel/bpf | |
parent | b76becde2b84137faa29bbc9a3b20953b5980e48 (diff) | |
download | linux-stable-106d45f350c7cac876844dc685845cba4ffdb70b.tar.gz linux-stable-106d45f350c7cac876844dc685845cba4ffdb70b.tar.bz2 linux-stable-106d45f350c7cac876844dc685845cba4ffdb70b.zip |
scsi: zfcp: fix request object use-after-free in send path causing wrong traces
When tracing instances where we open and close WKA ports, we also pass the
request-ID of the respective FSF command.
But after successfully sending the FSF command we must not use the
request-object anymore, as this might result in an use-after-free (see
"zfcp: fix request object use-after-free in send path causing seqno
errors" ).
To fix this add a new variable that caches the request-ID before sending
the request. This won't change during the hand-off to the FCP channel,
and so it's safe to trace this cached request-ID later, instead of using
the request object.
Signed-off-by: Benjamin Block <bblock@linux.ibm.com>
Fixes: d27a7cb91960 ("zfcp: trace on request for open and close of WKA port")
Cc: <stable@vger.kernel.org> #2.6.38+
Reviewed-by: Steffen Maier <maier@linux.ibm.com>
Reviewed-by: Jens Remus <jremus@linux.ibm.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'kernel/bpf')
0 files changed, 0 insertions, 0 deletions