From: Hannes Reinecke <hare@suse.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
Johannes Thumshirn <jth@kernel.org>,
James Bottomley <james.bottomley@hansenpartnership.com>,
Chad Dupuis <chad.dupuis@cavium.com>,
linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCHv2 0/7] libfc: sanitize kref and state machine fixes
Date: Fri, 30 Sep 2016 11:01:13 +0200 [thread overview]
Message-ID: <1475226080-60365-1-git-send-email-hare@suse.de> (raw)
Hi all,
here is the first round of patch to fixup libfc and FCoE.
It consists of a rewrite of the libfc rport kref handling
(or, to be precise, is _implements_ rport kref handling)
and updates the 'disc_mutex' handling to match the new
kref usage.
There are also some state machine fixes to handle FLOGI
better and a fix from Chad to harden FCoE login.
As usual, comments and reviews are welcome.
Changes to v1:
- Fixup typo in fc_lport.c
- Add review tags where applicable
Chad Dupuis (2):
libfc: Do not take rdata->rp_mutex when processing a -FC_EX_CLOSED ELS
response.
fcoe: Harden CVL handling when we have not logged into the fabric.
Hannes Reinecke (5):
libfc: Revisit kref handling
libfc: Fixup disc_mutex handling
libfc: Do not drop down to FLOGI for fc_rport_login()
libfc: Do not login if the port is already started
libfc: don't advance state machine for incoming FLOGI
drivers/scsi/fcoe/fcoe_ctlr.c | 72 ++++++++++++---
drivers/scsi/libfc/fc_disc.c | 38 +++++---
drivers/scsi/libfc/fc_lport.c | 9 +-
drivers/scsi/libfc/fc_rport.c | 197 ++++++++++++++++++++++++++++++++----------
4 files changed, 245 insertions(+), 71 deletions(-)
--
1.8.5.6
next reply other threads:[~2016-09-30 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 9:01 Hannes Reinecke [this message]
2016-09-30 9:01 ` [PATCHv2 1/7] libfc: Revisit kref handling Hannes Reinecke
2016-09-30 9:01 ` [PATCHv2 2/7] libfc: Fixup disc_mutex handling Hannes Reinecke
2016-09-30 9:01 ` [PATCHv2 3/7] libfc: Do not take rdata->rp_mutex when processing a -FC_EX_CLOSED ELS response Hannes Reinecke
2016-09-30 9:01 ` [PATCHv2 4/7] libfc: Do not drop down to FLOGI for fc_rport_login() Hannes Reinecke
2016-09-30 9:01 ` [PATCHv2 5/7] libfc: Do not login if the port is already started Hannes Reinecke
2016-09-30 9:01 ` [PATCHv2 6/7] libfc: don't advance state machine for incoming FLOGI Hannes Reinecke
2016-09-30 9:01 ` [PATCHv2 7/7] fcoe: Harden CVL handling when we have not logged into the fabric Hannes Reinecke
2016-10-11 21:07 ` [PATCHv2 0/7] libfc: sanitize kref and state machine fixes Martin K. Petersen
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=1475226080-60365-1-git-send-email-hare@suse.de \
--to=hare@suse.de \
--cc=chad.dupuis@cavium.com \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=jth@kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).