From: James Smart <jsmart2021@gmail.com>
To: linux-nvme@lists.infradead.org
Cc: linux-scsi@vger.kernel.org, kernel-janitors@vger.kernel.org,
paul.ely@broadcom.com, hare@suse.de, jejb@linux.ibm.com,
axboe@kernel.dk, martin.petersen@oracle.com, hch@infradead.org,
dan.carpenter@oracle.com, James Smart <jsmart2021@gmail.com>
Subject: [PATCH 0/3] lpfc: Fix errors in LS receive refactoring
Date: Wed, 20 May 2020 11:59:26 -0700 [thread overview]
Message-ID: <20200520185929.48779-1-jsmart2021@gmail.com> (raw)
A prior patch set refactored lpfc to create common routines for NVME LS
handling for use by both the initiator and target paths. The refactoring
introduced several errors spotted by additional testing and static checker
reporting.
This patch set corrects those errors.
The patches should enter via the nvme tree, as the lpfc modifications were
in support of nvme-fc transport api deltas merged via the nvme tree.
-- james
James Smart (3):
lpfc: Fix pointer checks and comments in LS receive refactoring
lpfc: fix axchg pointer reference after free and double frees
lpfc: Fix return value in __lpfc_nvme_ls_abort
drivers/scsi/lpfc/lpfc_nvme.c | 2 +-
drivers/scsi/lpfc/lpfc_nvmet.c | 29 ++++++++++++++++++-----------
drivers/scsi/lpfc/lpfc_sli.c | 10 ++++++----
3 files changed, 25 insertions(+), 16 deletions(-)
--
2.26.1
next reply other threads:[~2020-05-20 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 18:59 James Smart [this message]
2020-05-20 18:59 ` [PATCH 1/3] lpfc: Fix pointer checks and comments in LS receive refactoring James Smart
2020-05-20 18:59 ` [PATCH 2/3] lpfc: fix axchg pointer reference after free and double frees James Smart
2020-05-20 18:59 ` [PATCH 3/3] lpfc: Fix return value in __lpfc_nvme_ls_abort James Smart
2020-05-22 7:29 ` [PATCH 0/3] lpfc: Fix errors in LS receive refactoring Dan Carpenter
2020-05-26 14:53 ` Christoph Hellwig
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=20200520185929.48779-1-jsmart2021@gmail.com \
--to=jsmart2021@gmail.com \
--cc=axboe@kernel.dk \
--cc=dan.carpenter@oracle.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jejb@linux.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=paul.ely@broadcom.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;
as well as URLs for NNTP newsgroup(s).