From: Benjamin Block <bblock@linux.ibm.com>
To: "James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Benjamin Block <bblock@linux.ibm.com>,
Steffen Maier <maier@linux.ibm.com>,
Fedor Loshakov <loshakov@linux.ibm.com>,
Jens Remus <jremus@linux.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
linux-scsi@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [PATCH 0/3] zfcp: fixes for the zFCP device driver
Date: Tue, 2 Jul 2019 23:01:59 +0200 [thread overview]
Message-ID: <cover.1562098940.git.bblock@linux.ibm.com> (raw)
Hello James and Martin,
here are some fixes for the zFCP device driver. I am rather certain this
won't fit into this rc-cycle anymore.. I just found these last week and
with internal reviews and tests I was regrettably not able to post these
any sooner.
So please consider them for the next cycle. Or should I not have send
them in that case? Sorry, this step of the process was a bit unclear to
me.
The first patch is the "most urgent" of the three, although nothing
too terrible happens if we hit it.
Reviews are welcome from everyone, obviously.
Benjamin Block (3):
zfcp: fix request object use-after-free in send path causing seqno
errors
zfcp: fix request object use-after-free in send path causing wrong
traces
zfcp: fix GCC compiler warning emitted with -Wmaybe-uninitialized
drivers/s390/scsi/zfcp_erp.c | 7 +++++
drivers/s390/scsi/zfcp_fsf.c | 55 +++++++++++++++++++++++++++++++-----
2 files changed, 55 insertions(+), 7 deletions(-)
--
2.17.1
next reply other threads:[~2019-07-03 0:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 21:01 Benjamin Block [this message]
2019-07-02 21:02 ` [PATCH 1/3] zfcp: fix request object use-after-free in send path causing seqno errors Benjamin Block
2019-07-02 21:02 ` [PATCH 2/3] zfcp: fix request object use-after-free in send path causing wrong traces Benjamin Block
2019-07-02 21:02 ` [PATCH 3/3] zfcp: fix GCC compiler warning emitted with -Wmaybe-uninitialized Benjamin Block
2019-07-12 1:06 ` [PATCH 0/3] zfcp: fixes for the zFCP device driver Martin K. Petersen
2019-07-12 13:16 ` Benjamin Block
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=cover.1562098940.git.bblock@linux.ibm.com \
--to=bblock@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jejb@linux.ibm.com \
--cc=jremus@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=loshakov@linux.ibm.com \
--cc=maier@linux.ibm.com \
--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