zfcp features for v5.7
Subsystems (4)
cover zfcp features for v5.7
Martin, James,
one small zfcp fix and 2 features for v5.7.
Patches apply to Martin's 5.7/scsi-queue or James' misc branch.
Patch 1 is a small preventive fix with locking for point-to-point.
Patches 2..4 is a feature to expose fabric_name in fc_host sysfs.
Patches 5..8 is a feature to provide user information on the state of the otherwise transparent IBM Fibre Channel Endpoint Security. Patches 9..10 is a feature to add new recovery and corresponding kernel messages related to IBM Fibre Channel Endpoint Security.
[http://www.redbooks.ibm.com/redpieces/abstracts/sg248455.html?Open]
Jens Remus (6):
zfcp: auto variables for dereferenced structs in open port handler
zfcp: report FC Endpoint Security in sysfs
zfcp: log FC Endpoint Security of connections
zfcp: trace FC Endpoint Security of FCP devices and connections
zfcp: enhance handling of FC Endpoint Security errors
zfcp: log FC Endpoint Security errors
Steffen Maier (4):
zfcp: fix missing erp_lock in port recovery trigger for point-to-point
zfcp: expose fabric name as common fc_host sysfs attribute
zfcp: wire previously driver-specific sysfs attributes also to fc_host
zfcp: fix fc_host attributes that should be unknown on local link down
drivers/s390/scsi/zfcp_dbf.c | 44 ++++- drivers/s390/scsi/zfcp_dbf.h | 32 +++- drivers/s390/scsi/zfcp_def.h | 6 +- drivers/s390/scsi/zfcp_erp.c | 2 +- drivers/s390/scsi/zfcp_ext.h | 12 +- drivers/s390/scsi/zfcp_fsf.c | 290 ++++++++++++++++++++++++++++++--- drivers/s390/scsi/zfcp_fsf.h | 23 ++- drivers/s390/scsi/zfcp_scsi.c | 5 + drivers/s390/scsi/zfcp_sysfs.c | 70 +++++++- 9 files changed, 449 insertions(+), 35 deletions(-)
Signature · 1 line
2.17.1
PATCH 1/10 zfcp: fix missing erp_lock in port recovery trigger for point-to-point
v2.6.27 commit cc8c282963bd ("[SCSI] zfcp: Automatically attach remote ports") introduced zfcp automatic port scan.
Before that, the user had to use the sysfs attribute "port_add" of an FCP device (adapter) to add and open remote (target) ports, even for the remote peer port in point-to-point topology. That code path did a proper port open recovery trigger taking the erp_lock.
Since above commit, a new helper function zfcp_erp_open_ptp_port() performed an UNlocked port open recovery trigger. This can race with other parallel recovery triggers. In zfcp_erp_action_enqueue() this could corrupt e.g. adapter->erp_total_count or adapter->erp_ready_head.
As already found for fabric topology in v4.17 commit fa89adba1941 ("scsi: zfcp: fix infinite iteration on ERP ready list"), there was an endless loop during tracing of rport (un)block.
A subsequent v4.18 commit 9e156c54ace3 ("scsi: zfcp: assert that the ERP lock is held when tracing a recovery trigger") introduced a lockdep assertion for that case.
As a side effect, that lockdep assertion now uncovered the unlocked code path for PtP. It is from within an adapter ERP action:
zfcp_erp_strategy[1479] intentionally DROPs erp lock around
zfcp_erp_strategy_do_action()
zfcp_erp_strategy_do_action[1441] NO erp lock zfcp_erp_adapter_strategy[876] NO erp lock zfcp_erp_adapter_strategy_open[855] NO erp lock
zfcp_erp_adapter_strategy_open_fsf[806]NO erp lock zfcp_erp_adapter_strat_fsf_xconf[772] erp lock only around
zfcp_erp_action_to_running(), BUT *_not_* around zfcp_erp_enqueue_ptp_port()
zfcp_erp_enqueue_ptp_port[728] BUG: *_not_* taking erp lock _zfcp_erp_port_reopen[432] assumes to be called with erp lock zfcp_erp_action_enqueue[314] assumes to be called with erp lock zfcp_dbf_rec_trig[288] _checks_ to be called with erp lock: lockdep_assert_held(&adapter->erp_lock);
It causes the following lockdep warning:
WARNING: CPU: 2 PID: 775 at drivers/s390/scsi/zfcp_dbf.c:288
zfcp_dbf_rec_trig+0x16a/0x188
no locks held by zfcperp0.0.17c0/775.Fix this by using the proper locked recovery trigger helper function.
--- drivers/s390/scsi/zfcp_erp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/s390/scsi/zfcp_erp.c +1 -1
@@ -725,7 +725,7 @@ static void zfcp_erp_enqueue_ptp_port(struct zfcp_adapter *adapter) adapter->peer_d_id);if (IS_ERR (port))/* error or port already attached */ return ; -_zfcp_erp_port_reopen (port,0 ,"ereptp1" ); +zfcp_erp_port_reopen (port,0 ,"ereptp1" ); } static enum zfcp_erp_act_result zfcp_erp_adapter_strat_fsf_xconf(
Signature · 1 line
2.17.1
PATCH 3/10 zfcp: wire previously driver-specific sysfs attributes also to fc_host
In reply to Steffen MaierManufacturer, HBA model, firmware version, and hardware version. Use the same value format as for the driver-specific attributes. Keep the driver-specific attributes for stable user space sysfs API.
--- drivers/s390/scsi/zfcp_fsf.c | 11 +++++++++++ drivers/s390/scsi/zfcp_scsi.c | 4 ++++ 2 files changed, 15 insertions(+)
drivers/s390/scsi/zfcp_fsf.c +11 -0
@@ -502,6 +502,8 @@ static int zfcp_fsf_exchange_config_evaluate(struct zfcp_fsf_req *req)if (req->data)memcpy (req->data, bottom,sizeof (*bottom)); +snprintf (fc_host_manufacturer (shost),FC_SERIAL_NUMBER_SIZE ,"%s" , +"IBM" );fc_host_port_name (shost) =be64_to_cpu (nsp->fl_wwpn);fc_host_node_name (shost) =be64_to_cpu (nsp->fl_wwnn);fc_host_supported_classes (shost) =FC_COS_CLASS2 |FC_COS_CLASS3 ;
@@ -525,6 +527,8 @@ static int zfcp_fsf_exchange_config_evaluate(struct zfcp_fsf_req *req)zfcp_fsf_convert_portspeed (bottom->fc_link_speed); adapter->hydra_version = bottom->adapter_type; +snprintf (fc_host_model (shost),FC_SYMBOLIC_NAME_SIZE ,"0x%04x" , + bottom->adapter_type);switch (bottom->fc_topology) {case FSF_TOPO_P2P :
@@ -569,6 +573,8 @@ static void zfcp_fsf_exchange_config_data_handler(struct zfcp_fsf_req *req)if (req->status &ZFCP_STATUS_FSFREQ_ERROR )return ; +snprintf (fc_host_firmware_version (shost),FC_VERSION_STRING_SIZE , +"0x%08x" , bottom->lic_version); adapter->fsf_lic_version = bottom->lic_version; adapter->adapter_features = bottom->adapter_features; adapter->connection_features = bottom->connection_features;
@@ -609,6 +615,8 @@ static void zfcp_fsf_exchange_config_data_handler(struct zfcp_fsf_req *req)fc_host_speed (shost) =FC_PORTSPEED_UNKNOWN ;fc_host_port_type (shost) =FC_PORTTYPE_UNKNOWN ; adapter->hydra_version =0 ; +snprintf (fc_host_model (shost),FC_SYMBOLIC_NAME_SIZE ,"0x%04x" , +0 );/* avoids adapter shutdown to be able to recognize * events such as LINK UP */
@@ -626,6 +634,9 @@ static void zfcp_fsf_exchange_config_data_handler(struct zfcp_fsf_req *req)if (adapter->adapter_features &FSF_FEATURE_HBAAPI_MANAGEMENT ) { adapter->hardware_version = bottom->hardware_version; +snprintf (fc_host_hardware_version (shost), +FC_VERSION_STRING_SIZE , +"0x%08x" , bottom->hardware_version);memcpy (fc_host_serial_number (shost), bottom->serial_number,min (FC_SERIAL_NUMBER_SIZE ,17 )); EBCASC(fc_host_serial_number(shost),
drivers/s390/scsi/zfcp_scsi.c +4 -0
@@ -856,6 +856,10 @@ struct fc_function_template zfcp_transport_functions = { .show_host_supported_speeds = 1, .show_host_maxframe_size = 1, .show_host_serial_number = 1, + .show_host_manufacturer = 1, + .show_host_model = 1, + .show_host_hardware_version = 1, + .show_host_firmware_version = 1, .get_fc_host_stats = zfcp_scsi_get_fc_host_stats, .reset_fc_host_stats = zfcp_scsi_reset_fc_host_stats, .set_rport_dev_loss_tmo = zfcp_scsi_set_rport_dev_loss_tmo,
Signature · 1 line
2.17.1
PATCH 4/10 zfcp: fix fc_host attributes that should be unknown on local link down
In reply to Steffen MaierWhen we get an unsolicited notification on local link went down, zfcp_fsf_status_read_link_down() calls zfcp_fsf_link_down_info_eval(). This only blocks rports, and sets ZFCP_STATUS_ADAPTER_LINK_UNPLUGGED and ZFCP_STATUS_COMMON_ERP_FAILED. Only the fc_host port_state changes to "Linkdown", because zfcp_scsi_get_host_port_state() is an active callback and uses the adapter status.
Other fc_host attributes model, port_id, port_type, speed, fabric_name (and zfcp device attributes card_version, peer_wwpn, peer_wwnn, peer_d_id) which depend on a local link, continued to show their last known "good" value.
Only if something triggered an exchange config data, some values were updated to their unknown equivalent via case FSF_EXCHANGE_CONFIG_DATA_INCOMPLETE due to local link down. Triggers for exchange config data are adapter recovery, or reading any of the following zfcp-specific scsi host sysfs attributes "requests", "megabytes", or "seconds_active" in /sys/devices/css*/*.*.*/*.*.*/host*/scsi_host/host*/.
The other fc_host attributes active_fc4s and permanent_port_name continued to show their last known "good" value.
Only if something triggered an exchange port data, some values changed. Active_fc4s became all zeros as unknown equivalent during link down. Permanent_port_name does not depend on a local link. But for non-NPIV FCP devices, permanent_port_name erroneously became whatever value fc_host port_name had at that point in time (see previous paragraph). Triggers for exchange port data are the zfcp-specific scsi host sysfs attribute "utilization", or [{reset,get}_fc_host_stats]
write anything into "reset_statistics" or read any of the other attributes under /sys/devices/css*/*.*.*/*.*.*/host*/fc_host/host*/statistics/.
(cf. v4.9 commit bd77befa5bcf ("zfcp: fix fc_host port_type with NPIV"))
This is particularly confusing when using "lszfcp -b <fcpdevbusid> -Ha" or dbginfo.sh which read fc_host attributes and also scsi_host attributes. After link down, the first invocation produces (abbreviated):
Class = "fc_host"
active_fc4s = "0x00 0x00 0x01 0x00 ..."
...
fabric_name = "0x10000027f8e04c49"
...
permanent_port_name = "0xc05076e4588059c1"
port_id = "0x244800"
port_state = "Linkdown"
port_type = "NPort (fabric via point-to-point)"
...
speed = "16 Gbit"Class = "scsi_host"
...
megabytes = "0 0"
...
requests = "0 0 0"
seconds_active = "37"
...
utilization = "0 0 0"
The second and next invocations produce (abbreviated):
Class = "fc_host"
active_fc4s = "0x00 0x00 0x00 0x00 ..."
...
fabric_name = "0x0"
...
permanent_port_name = "0x0"
port_id = "0x000000"
port_state = "Linkdown"
port_type = "Unknown"
...
speed = "unknown"Class = "scsi_host"
...
megabytes = "0 0"
...
requests = "0 0 0"
seconds_active = "38"
...
utilization = "0 0 0"
Factor out the resetting of local link dependent fc_host attributes from zfcp_fsf_exchange_config_data_handler() case FSF_EXCHANGE_CONFIG_DATA_INCOMPLETE into a new helper function zfcp_fsf_fc_host_link_down().
All code places that detect local link down (SRB, FSF_PROT_LINK_DOWN, xconf data/port incomplete) call zfcp_fsf_link_down_info_eval(). Call the new helper from there. This works because zfcp_fsf_link_down_info_eval() and thus the helper is called before zfcp_fsf_exchange_{config,port}_evaluate().
Port_name and node_name are always valid, so never reset them.
Get the permanent_port_name from exchange port data unconditionally as it always has a valid known good value, even during link down.
Note: Rather than hardcode in zfcp_fsf_exchange_config_evaluate(), fc_host supported_classes could theoretically get its value from fsf_qtcb_bottom_port.class_of_service in zfcp_fsf_exchange_port_evaluate().
When the link comes back, we get a different notification, perform adapter recovery, and this triggers an implicit exchange config data followed by exchange port data filling in the link dependent fc_host attributes with known good values again.
--- drivers/s390/scsi/zfcp_fsf.c | 39 +++++++++++++++++++----------------- 1 file changed, 21 insertions(+), 18 deletions(-)
drivers/s390/scsi/zfcp_fsf.c +21 -18
@@ -120,6 +120,23 @@ static void zfcp_fsf_status_read_port_closed(struct zfcp_fsf_req *req)read_unlock_irqrestore (&adapter->port_list_lock, flags); } +static void zfcp_fsf_fc_host_link_down (struct zfcp_adapter *adapter) +{ +struct Scsi_Host *shost = adapter->scsi_host; + +fc_host_port_id (shost) =0 ; +fc_host_fabric_name (shost) =0 ; +fc_host_speed (shost) =FC_PORTSPEED_UNKNOWN ; +fc_host_port_type (shost) =FC_PORTTYPE_UNKNOWN ; + adapter->hydra_version =0 ; +snprintf (fc_host_model (shost),FC_SYMBOLIC_NAME_SIZE ,"0x%04x" ,0 ); +memset (fc_host_active_fc4s (shost),0 ,FC_FC4_LIST_SIZE ); + + adapter->peer_wwpn =0 ; + adapter->peer_wwnn =0 ; + adapter->peer_d_id =0 ; +} +static void zfcp_fsf_link_down_info_eval (struct zfcp_fsf_req *req,struct fsf_link_down_info *link_down) {
@@ -132,6 +149,8 @@ static void zfcp_fsf_link_down_info_eval(struct zfcp_fsf_req *req,zfcp_scsi_schedule_rports_block (adapter); +zfcp_fsf_fc_host_link_down (adapter); +if (!link_down) goto out;
@@ -512,9 +531,6 @@ static int zfcp_fsf_exchange_config_evaluate(struct zfcp_fsf_req *req) adapter->stat_read_buf_num =max (bottom->status_read_buf_num, (u16 )FSF_STATUS_READS_RECOM ); -if (fc_host_permanent_port_name (shost) ==-1 ) -fc_host_permanent_port_name (shost) =fc_host_port_name (shost); -zfcp_scsi_set_prot (adapter);/* no error return above here, otherwise must fix call chains */
@@ -608,16 +624,6 @@ static void zfcp_fsf_exchange_config_data_handler(struct zfcp_fsf_req *req)zfcp_diag_update_xdata (diag_hdr, bottom, true); req->status |=ZFCP_STATUS_FSFREQ_XDATAINCOMPLETE ; -fc_host_node_name (shost) =0 ; -fc_host_port_name (shost) =0 ; -fc_host_port_id (shost) =0 ; -fc_host_fabric_name (shost) =0 ; -fc_host_speed (shost) =FC_PORTSPEED_UNKNOWN ; -fc_host_port_type (shost) =FC_PORTTYPE_UNKNOWN ; - adapter->hydra_version =0 ; -snprintf (fc_host_model (shost),FC_SYMBOLIC_NAME_SIZE ,"0x%04x" , -0 ); -/* avoids adapter shutdown to be able to recognize * events such as LINK UP */ atomic_or(ZFCP_STATUS_ADAPTER_XCONFIG_OK,
@@ -667,10 +673,7 @@ static void zfcp_fsf_exchange_port_evaluate(struct zfcp_fsf_req *req)if (req->data)memcpy (req->data, bottom,sizeof (*bottom)); -if (adapter->connection_features &FSF_FEATURE_NPIV_MODE ) { -fc_host_permanent_port_name (shost) = bottom->wwpn; - }else -fc_host_permanent_port_name (shost) =fc_host_port_name (shost); +fc_host_permanent_port_name (shost) = bottom->wwpn;fc_host_maxframe_size (shost) = bottom->maximum_frame_size;fc_host_supported_speeds (shost) =zfcp_fsf_convert_portspeed (bottom->supported_speed);
@@ -704,9 +707,9 @@ static void zfcp_fsf_exchange_port_data_handler(struct zfcp_fsf_req *req)zfcp_diag_update_xdata (diag_hdr, bottom, true); req->status |=ZFCP_STATUS_FSFREQ_XDATAINCOMPLETE ; -zfcp_fsf_exchange_port_evaluate (req);zfcp_fsf_link_down_info_eval (req, &qtcb->header.fsf_status_qual.link_down_info); +zfcp_fsf_exchange_port_evaluate (req);break ; } }
Signature · 1 line
2.17.1
PATCH 7/10 zfcp: log FC Endpoint Security of connections
In reply to Steffen MaierFrom: Jens Remus <[email protected]>
Log the usage of and subsequent changes in FC Endpoint Security of connections between FCP devices and FC remote ports to the kernel ring buffer. Activation of FC Endpoint Security is logged as informational. Change and deactivation are logged as warning.
No logging takes place, if FC Endpoint Security is not used (i.e. never activated) on a connection or if it does not change during reopen of a port (e.g. due to adapter or port recovery).
--- drivers/s390/scsi/zfcp_def.h | 1 + drivers/s390/scsi/zfcp_fsf.c | 54 +++++++++++++++++++++++++++++++++++- 2 files changed, 54 insertions(+), 1 deletion(-)
drivers/s390/scsi/zfcp_def.h +1 -0
@@ -220,6 +220,7 @@ struct zfcp_port {u32 maxframe_size;u32 supported_classes;u32 connection_info; +u32 connection_info_old;struct work_struct gid_pn_work;struct work_struct test_link_work;struct work_struct rport_work;
drivers/s390/scsi/zfcp_fsf.c +53 -1
84 lines not on this page · raw message
Signature · 1 line
2.17.1
PATCH 8/10 zfcp: trace FC Endpoint Security of FCP devices and connections
In reply to Steffen MaierFrom: Jens Remus <[email protected]>
Trace changes in Fibre Channel Endpoint Security capabilities of FCP devices as well as changes in Fibre Channel Endpoint Security state of their connections to FC remote ports as FC Endpoint Security changes with trace level 3 in HBA DBF.
A change in FC Endpoint Security capabilities of FCP devices is traced as response to FSF command FSF_QTCB_EXCHANGE_PORT_DATA with a trace tag of "fsfcesa" and a WWPN of ZFCP_DBF_INVALID_WWPN = 0x0000000000000000 (see FC-FS-4 §18 "Name_Identifier Formats", NAA field).
A change in FC Endpoint Security state of connections between FCP devices and FC remote ports is traced as response to FSF command FSF_QTCB_OPEN_PORT_WITH_DID with a trace tag of "fsfcesp".
Example trace record of FC Endpoint Security capability change of FCP device formatted with zfcpdbf from s390-tools:
Timestamp : ...
Area : HBA
Subarea : 00
Level : 3
Exception : -
CPU ID : ...
Caller : 0x...
Record ID : 5 ZFCP_DBF_HBA_FCES
Tag : fsfcesa FSF FC Endpoint Security adapter
Request ID : 0x...
Request status : 0x00000010
FSF cmnd : 0x0000000e FSF_QTCB_EXCHANGE_PORT_DATA
FSF sequence no: 0x...
FSF issued : ...
FSF stat : 0x00000000 FSF_GOOD
FSF stat qual : n/a
Prot stat : n/a
Prot stat qual : n/a
Port handle : 0x00000000 none (invalid)
LUN handle : n/a
WWPN : 0x0000000000000000 ZFCP_DBF_INVALID_WWPN
FCES old : 0x00000000 old FC Endpoint Security
FCES new : 0x00000007 new FC Endpoint Security
Example trace record of FC Endpoint Security change of connection to FC remote port formatted with zfcpdbf from s390-tools:
Timestamp : ...
Area : HBA
Subarea : 00
Level : 3
Exception : -
CPU ID : ...
Caller : 0x...
Record ID : 5 ZFCP_DBF_HBA_FCES
Tag : fsfcesp FSF FC Endpoint Security port
Request ID : 0x...
Request status : 0x00000010
FSF cmnd : 0x00000005 FSF_QTCB_OPEN_PORT_WITH_DID
FSF sequence no: 0x...
FSF issued : ...
FSF stat : 0x00000000 FSF_GOOD
FSF stat qual : n/a
Prot stat : n/a
Prot stat qual : n/a
Port handle : 0x...
WWPN : 0x500507630401120c WWPN
FCES old : 0x00000000 old FC Endpoint Security
FCES new : 0x00000004 new FC Endpoint Security
--- drivers/s390/scsi/zfcp_dbf.c | 44 +++++++++++++++++++++++++++++++++++- drivers/s390/scsi/zfcp_dbf.h | 32 ++++++++++++++++++++++---- drivers/s390/scsi/zfcp_def.h | 1 + drivers/s390/scsi/zfcp_ext.h | 3 +++ drivers/s390/scsi/zfcp_fsf.c | 28 ++++++++++++++++++++--- 5 files changed, 100 insertions(+), 8 deletions(-)
drivers/s390/scsi/zfcp_dbf.c +43 -1
@@ -4,7 +4,7 @@* * Debug traces for zfcp. * -* Copyright IBM Corp. 2002, 2018 +* Copyright IBM Corp. 2002, 2020 */ #define KMSG_COMPONENT "zfcp"
@@ -103,6 +103,48 @@ void zfcp_dbf_hba_fsf_res(char *tag, int level, struct zfcp_fsf_req *req)spin_unlock_irqrestore (&dbf->hba_lock, flags); } +/** +* zfcp_dbf_hba_fsf_fces - trace event for fsf responses related to +* FC Endpoint Security (FCES) +* @tag: tag indicating which kind of FC Endpoint Security event has occurred +* @req: request for which a response was received +* @wwpn: remote port or ZFCP_DBF_INVALID_WWPN +* @fc_security_old: old FC Endpoint Security of FCP device or connection +* @fc_security_new: new FC Endpoint Security of FCP device or connection +*/ +void zfcp_dbf_hba_fsf_fces (char *tag,const struct zfcp_fsf_req *req,u64 wwpn, +u32 fc_security_old,u32 fc_security_new) +{ +struct zfcp_dbf *dbf = req->adapter->dbf; +struct fsf_qtcb_prefix *q_pref = &req->qtcb->prefix; +struct fsf_qtcb_header *q_head = &req->qtcb->header; +struct zfcp_dbf_hba *rec = &dbf->hba_buf; +static int const level =3 ; +unsigned long flags; + +if (unlikely (!debug_level_enabled (dbf->hba, level))) +return ; + +spin_lock_irqsave (&dbf->hba_lock, flags); +memset (rec,0 ,sizeof (*rec)); + +memcpy (rec->tag, tag,ZFCP_DBF_TAG_LEN ); + rec->id =ZFCP_DBF_HBA_FCES ; + rec->fsf_req_id = req->req_id; + rec->fsf_req_status = req->status; + rec->fsf_cmd = q_head->fsf_command; + rec->fsf_seq_no = q_pref->req_seq_no; + rec->u.fces.req_issued = req->issued; + rec->u.fces.fsf_status = q_head->fsf_status; + rec->u.fces.port_handle = q_head->port_handle; + rec->u.fces.wwpn = wwpn; + rec->u.fces.fc_security_old = fc_security_old; + rec->u.fces.fc_security_new = fc_security_new; + +debug_event (dbf->hba, level, rec,sizeof (*rec)); +spin_unlock_irqrestore (&dbf->hba_lock, flags); +} +/** * zfcp_dbf_hba_fsf_uss - trace event for an unsolicited status buffer * @tag: tag indicating which kind of unsolicited status has been received
drivers/s390/scsi/zfcp_dbf.h +28 -4
@@ -3,7 +3,7 @@* zfcp device driver * debug feature declarations * -* Copyright IBM Corp. 2008, 2017 +* Copyright IBM Corp. 2008, 2020 */ #ifndef ZFCP_DBF_H
@@ -16,6 +16,7 @@#define ZFCP_DBF_TAG_LEN 7 +#define ZFCP_DBF_INVALID_WWPN 0x0000000000000000ull#define ZFCP_DBF_INVALID_LUN 0xFFFFFFFFFFFFFFFFullenum zfcp_dbf_pseudo_erp_act_type {
@@ -157,18 +158,39 @@ struct zfcp_dbf_hba_uss {u64 queue_designator; } __packed; +/** +* struct zfcp_dbf_hba_fces - trace record for FC Endpoint Security +* @req_issued: timestamp when request was issued +* @fsf_status: fsf status +* @port_handle: handle for port +* @wwpn: remote FC port WWPN +* @fc_security_old: old FC Endpoint Security +* @fc_security_new: new FC Endpoint Security +* +*/ +struct zfcp_dbf_hba_fces { +u64 req_issued; +u32 fsf_status; +u32 port_handle; +u64 wwpn; +u32 fc_security_old; +u32 fc_security_new; +} __packed; +/** * enum zfcp_dbf_hba_id - HBA trace record identifier * @ZFCP_DBF_HBA_RES: response trace record * @ZFCP_DBF_HBA_USS: unsolicited status trace record * @ZFCP_DBF_HBA_BIT: bit error trace record * @ZFCP_DBF_HBA_BASIC: basic adapter event, only trace tag, no other data +* @ZFCP_DBF_HBA_FCES: FC Endpoint Security trace record */ enum zfcp_dbf_hba_id {ZFCP_DBF_HBA_RES =1 ,ZFCP_DBF_HBA_USS =2 ,ZFCP_DBF_HBA_BIT =3 ,ZFCP_DBF_HBA_BASIC =4 , +ZFCP_DBF_HBA_FCES =5 , };/**
@@ -181,9 +203,10 @@ enum zfcp_dbf_hba_id {* @fsf_seq_no: fsf sequence number * @pl_len: length of payload stored as zfcp_dbf_pay * @u: record type specific data -* @u.res: data for fsf responses -* @u.uss: data for unsolicited status buffer -* @u.be: data for bit error unsolicited status buffer +* @u.res: data for fsf responses +* @u.uss: data for unsolicited status buffer +* @u.be: data for bit error unsolicited status buffer +* @u.fces: data for FC Endpoint Security */ struct zfcp_dbf_hba {u8 id;
@@ -197,6 +220,7 @@ struct zfcp_dbf_hba {struct zfcp_dbf_hba_res res;struct zfcp_dbf_hba_uss uss;struct fsf_bit_error_payload be; +struct zfcp_dbf_hba_fces fces; } u; } __packed;
drivers/s390/scsi/zfcp_def.h +1 -0
@@ -159,6 +159,7 @@ struct zfcp_adapter {u32 connection_features;/* host connection features */ u32 hardware_version;/* of FCP channel */ u32 fc_security_algorithms;/* of FCP channel */ +u32 fc_security_algorithms_old;/* of FCP channel */ u16 timer_ticks;/* time int for a tick */ struct Scsi_Host *scsi_host;/* Pointer to mid-layer */ struct list_head port_list;/* remote port list */
drivers/s390/scsi/zfcp_ext.h +3 -0
@@ -44,6 +44,9 @@ extern void zfcp_dbf_rec_run_lvl(int level, char *tag,extern void zfcp_dbf_rec_run_wka (char *,struct zfcp_fc_wka_port *,u64 );extern void zfcp_dbf_hba_fsf_uss (char *,struct zfcp_fsf_req *);extern void zfcp_dbf_hba_fsf_res (char *,int ,struct zfcp_fsf_req *); +extern void zfcp_dbf_hba_fsf_fces (char *tag,const struct zfcp_fsf_req *req, +u64 wwpn,u32 fc_security_old, +u32 fc_security_new);extern void zfcp_dbf_hba_bit_err (char *,struct zfcp_fsf_req *);extern void zfcp_dbf_hba_def_err (struct zfcp_adapter *,u64 ,u16 ,void **);extern void zfcp_dbf_hba_basic (char *,struct zfcp_adapter *);
drivers/s390/scsi/zfcp_fsf.c +25 -3
@@ -741,6 +741,22 @@ ssize_t zfcp_fsf_scnprint_fc_security(char *buf, size_t size, u32 fc_security,return len; } +static void zfcp_fsf_dbf_adapter_fc_security (struct zfcp_adapter *adapter, +struct zfcp_fsf_req *req) +{ +if (adapter->fc_security_algorithms == + adapter->fc_security_algorithms_old) { +/* no change, no trace */ +return ; + } + +zfcp_dbf_hba_fsf_fces ("fsfcesa" , req,ZFCP_DBF_INVALID_WWPN , + adapter->fc_security_algorithms_old, + adapter->fc_security_algorithms); + + adapter->fc_security_algorithms_old = adapter->fc_security_algorithms; +} +static void zfcp_fsf_exchange_port_evaluate (struct zfcp_fsf_req *req) {struct zfcp_adapter *adapter = req->adapter;
@@ -763,6 +779,7 @@ static void zfcp_fsf_exchange_port_evaluate(struct zfcp_fsf_req *req) bottom->fc_security_algorithms; else adapter->fc_security_algorithms = 0; +zfcp_fsf_dbf_adapter_fc_security (adapter, req); }static void zfcp_fsf_exchange_port_data_handler (struct zfcp_fsf_req *req)
@@ -1579,16 +1596,21 @@ int zfcp_fsf_exchange_port_data_sync(struct zfcp_qdio *qdio,return retval; } -static void zfcp_fsf_log_port_fc_security (struct zfcp_port *port) +static void zfcp_fsf_log_port_fc_security (struct zfcp_port *port, +struct zfcp_fsf_req *req) {char mnemonic_old[ZFCP_FSF_MAX_FC_SECURITY_MNEMONIC_LENGTH ];char mnemonic_new[ZFCP_FSF_MAX_FC_SECURITY_MNEMONIC_LENGTH ];if (port->connection_info == port->connection_info_old) { -/* no change, no log */ +/* no change, no log nor trace */ return ; } +zfcp_dbf_hba_fsf_fces ("fsfcesp" , req, port->wwpn, + port->connection_info_old, + port->connection_info); +zfcp_fsf_scnprint_fc_security (mnemonic_old,sizeof (mnemonic_old), port->connection_info_old,ZFCP_FSF_PRINT_FMT_SINGLEITEM );
@@ -1663,7 +1685,7 @@ static void zfcp_fsf_open_port_handler(struct zfcp_fsf_req *req) port->connection_info = bottom->connection_info; else port->connection_info = 0; -zfcp_fsf_log_port_fc_security (port); +zfcp_fsf_log_port_fc_security (port, req);atomic_or (ZFCP_STATUS_COMMON_OPEN |ZFCP_STATUS_PORT_PHYS_OPEN , &port->status); atomic_andnot(ZFCP_STATUS_COMMON_ACCESS_BOXED,
Signature · 1 line
2.17.1
PATCH 2/10 zfcp: expose fabric name as common fc_host sysfs attribute
In reply to Steffen MaierFICON Express8S or older, as well as card features newer than FICON Express16S+ have no certain firmware level requirement.
FICON Express16S or FICON Express16S+ have the following minimum firmware level requirements to show a proper fabric name value:
z13 machine
FICON Express16S , MCL P08424.005 , LIC version 0x00000721
z14 machine
FICON Express16S , MCL P42611.008 , LIC version 0x10200069 FICON Express16S+ , MCL P42625.010 , LIC version 0x10300147
Otherwise, the read value is not the fabric name.
Each FCP channel of these card features might need one SAN fabric re-login after concurrent microcode update, in order to show the proper fabric name. Possible ways to trigger a SAN fabric re-login are one of:
Pull fibres between FCP channel port and SAN switch port on either side and re-plug, disable SAN switch port adjacent to FCP channel port and re-enable switch port, or at Service Element toggle off all CHPIDs of FCP channel over all LPARs and toggle CHPIDs on again.
Zfcp operating subchannels (FCP devices) on such FCP channel recovers a fabric re-login.
Initialize fabric name for any topology and have it an invalid WWPN 0x0 for anything but fabric topology.
Otherwise for e.g. point-to-point topology one could see the initial -1 from fc_host_setup() and after a link unplug our fabric name would turn to 0x0 (with subsequent commit ("zfcp: fix fc_host attributes that should be unknown on local link down)) and stay 0x0 on link replug. I did not initialize to 0x0 somewhere even earlier in the code path such that it would not flap from real to 0x0 to real on e.g. an exchange config data with fabric topology.
--- drivers/s390/scsi/zfcp_fsf.c | 5 +++++ drivers/s390/scsi/zfcp_scsi.c | 1 + 2 files changed, 6 insertions(+)
drivers/s390/scsi/zfcp_fsf.c +5 -0
@@ -532,8 +532,10 @@ static int zfcp_fsf_exchange_config_evaluate(struct zfcp_fsf_req *req) adapter->peer_wwpn =be64_to_cpu (plogi->fl_wwpn); adapter->peer_wwnn =be64_to_cpu (plogi->fl_wwnn);fc_host_port_type (shost) =FC_PORTTYPE_PTP ; +fc_host_fabric_name (shost) =0 ;break ;case FSF_TOPO_FABRIC : +fc_host_fabric_name (shost) =be64_to_cpu (plogi->fl_wwnn);if (bottom->connection_features &FSF_FEATURE_NPIV_MODE )fc_host_port_type (shost) =FC_PORTTYPE_NPIV ;else
@@ -541,8 +543,10 @@ static int zfcp_fsf_exchange_config_evaluate(struct zfcp_fsf_req *req)break ;case FSF_TOPO_AL :fc_host_port_type (shost) =FC_PORTTYPE_NLPORT ; +fc_host_fabric_name (shost) =0 ;/* fall through */ default : +fc_host_fabric_name (shost) =0 ;dev_err (&adapter->ccw_device->dev,"Unknown or unsupported arbitrated loop " "fibre channel topology detected\n" );
@@ -601,6 +605,7 @@ static void zfcp_fsf_exchange_config_data_handler(struct zfcp_fsf_req *req)fc_host_node_name (shost) =0 ;fc_host_port_name (shost) =0 ;fc_host_port_id (shost) =0 ; +fc_host_fabric_name (shost) =0 ;fc_host_speed (shost) =FC_PORTSPEED_UNKNOWN ;fc_host_port_type (shost) =FC_PORTTYPE_UNKNOWN ; adapter->hydra_version =0 ;
drivers/s390/scsi/zfcp_scsi.c +1 -0
@@ -871,5 +871,6 @@ struct fc_function_template zfcp_transport_functions = { .show_host_symbolic_name = 1, .show_host_speed = 1, .show_host_port_id = 1, + .show_host_fabric_name = 1, .dd_bsg_size = sizeof(struct zfcp_fsf_ct_els), };
Signature · 1 line
2.17.1
PATCH 5/10 zfcp: auto variables for dereferenced structs in open port handler
In reply to Steffen MaierFrom: Jens Remus <[email protected]>
Introduce automatic variables for adapter and QTCB bottom in zfcp_fsf_open_port_handler(). This facilitates subsequent changes to meet the 80 character per line limit.
--- drivers/s390/scsi/zfcp_fsf.c | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-)
drivers/s390/scsi/zfcp_fsf.c +7 -6
@@ -4,7 +4,7 @@* * Implementation of FSF commands. * -* Copyright IBM Corp. 2002, 2018 +* Copyright IBM Corp. 2002, 2020 */ #define KMSG_COMPONENT "zfcp"
@@ -1499,8 +1499,10 @@ int zfcp_fsf_exchange_port_data_sync(struct zfcp_qdio *qdio,static void zfcp_fsf_open_port_handler (struct zfcp_fsf_req *req) { +struct zfcp_adapter *adapter = req->adapter;struct zfcp_port *port = req->data;struct fsf_qtcb_header *header = &req->qtcb->header; +struct fsf_qtcb_bottom_support *bottom = &req->qtcb->bottom.support;struct fc_els_flogi *plogi;if (req->status &ZFCP_STATUS_FSFREQ_ERROR )
@@ -1510,7 +1512,7 @@ static void zfcp_fsf_open_port_handler(struct zfcp_fsf_req *req)case FSF_PORT_ALREADY_OPEN :break ;case FSF_MAXIMUM_NUMBER_OF_PORTS_EXCEEDED : -dev_warn (&req->adapter->ccw_device->dev, +dev_warn (&adapter->ccw_device->dev,"Not enough FCP adapter resources to open " "remote port 0x%016Lx\n" , (unsigned long long )port->wwpn);
@@ -1550,10 +1552,9 @@ static void zfcp_fsf_open_port_handler(struct zfcp_fsf_req *req)* another GID_PN straight after a port has been opened. * Alternately, an ADISC/PDISC ELS should suffice, as well. */ - plogi = (struct fc_els_flogi *) req->qtcb->bottom.support.els; -if (req->qtcb->bottom.support.els1_length >= -FSF_PLOGI_MIN_LEN ) -zfcp_fc_plogi_evaluate (port, plogi); + plogi = (struct fc_els_flogi *) bottom->els; +if (bottom->els1_length >=FSF_PLOGI_MIN_LEN ) +zfcp_fc_plogi_evaluate (port, plogi);break ;case FSF_UNKNOWN_OP_SUBTYPE : req->status |=ZFCP_STATUS_FSFREQ_ERROR ;
Signature · 1 line
2.17.1
PATCH 6/10 zfcp: report FC Endpoint Security in sysfs
In reply to Steffen MaierFrom: Jens Remus <[email protected]>
Add an interface to read Fibre Channel Endpoint Security information of FCP channels and their connections to FC remote ports. It comes in the form of new sysfs attributes that are attached to the CCW device representing the FCP device and its zfcp port objects.
The read-only sysfs attribute "fc_security" of a CCW device representing a FCP device shows the FC Endpoint Security capabilities of the device. Possible values are: "unknown", "unsupported", "none", or a comma- separated list of one or more mnemonics and/or one hexadecimal value representing the supported FC Endpoint Security:
Authentication: Authentication supported
Encryption : Encryption supported
The read-only sysfs attribute "fc_security" of a zfcp port object shows the FC Endpoint Security used on the connection between its parent FCP device and the FC remote port. Possible values are: "unknown", "unsupported", "none", or a mnemonic or hexadecimal value representing the FC Endpoint Security used:
Authentication: Connection has been authenticated
Encryption : Connection is encrypted
Both sysfs attributes may return hexadecimal values instead of mnemonics, if the mnemonic lookup table does not contain an entry for the FC Endpoint Security reported by the FCP device.
--- drivers/s390/scsi/zfcp_def.h | 4 +- drivers/s390/scsi/zfcp_ext.h | 9 +++- drivers/s390/scsi/zfcp_fsf.c | 79 ++++++++++++++++++++++++++++++++++ drivers/s390/scsi/zfcp_fsf.h | 14 ++++-- drivers/s390/scsi/zfcp_sysfs.c | 70 +++++++++++++++++++++++++++++- 5 files changed, 170 insertions(+), 6 deletions(-)
drivers/s390/scsi/zfcp_def.h +3 -1
@@ -4,7 +4,7 @@* * Global definitions for the zfcp device driver. * -* Copyright IBM Corp. 2002, 2018 +* Copyright IBM Corp. 2002, 2020 */ #ifndef ZFCP_DEF_H
@@ -158,6 +158,7 @@ struct zfcp_adapter {u32 adapter_features;/* FCP channel features */ u32 connection_features;/* host connection features */ u32 hardware_version;/* of FCP channel */ +u32 fc_security_algorithms;/* of FCP channel */ u16 timer_ticks;/* time int for a tick */ struct Scsi_Host *scsi_host;/* Pointer to mid-layer */ struct list_head port_list;/* remote port list */
@@ -218,6 +219,7 @@ struct zfcp_port {atomic_t erp_counter;u32 maxframe_size;u32 supported_classes; +u32 connection_info;struct work_struct gid_pn_work;struct work_struct test_link_work;struct work_struct rport_work;
drivers/s390/scsi/zfcp_ext.h +8 -1
@@ -4,7 +4,7 @@* * External function declarations. * -* Copyright IBM Corp. 2002, 2018 +* Copyright IBM Corp. 2002, 2020 */ #ifndef ZFCP_EXT_H
@@ -135,6 +135,13 @@ extern struct zfcp_fsf_req *zfcp_fsf_fcp_task_mgmt(struct scsi_device *sdev, u8 tm_flags);extern struct zfcp_fsf_req *zfcp_fsf_abort_fcp_cmnd (struct scsi_cmnd *);extern void zfcp_fsf_reqid_check (struct zfcp_qdio *,int ); +enum zfcp_fsf_print_fmt { +ZFCP_FSF_PRINT_FMT_LIST , +ZFCP_FSF_PRINT_FMT_SINGLEITEM , +}; +extern ssize_t zfcp_fsf_scnprint_fc_security (char *buf,size_t size, +u32 fc_security, +enum zfcp_fsf_print_fmt fmt);/* zfcp_qdio.c */ extern int zfcp_qdio_setup (struct zfcp_adapter *);
drivers/s390/scsi/zfcp_fsf.c +79 -0
97 lines not on this page · raw message
drivers/s390/scsi/zfcp_fsf.h +11 -3
@@ -4,7 +4,7 @@* * Interface to the FSF support functions. * -* Copyright IBM Corp. 2002, 2018 +* Copyright IBM Corp. 2002, 2020 */ #ifndef FSF_H
@@ -165,6 +165,7 @@#define FSF_FEATURE_MEASUREMENT_DATA 0x00000200#define FSF_FEATURE_REQUEST_SFP_DATA 0x00000200#define FSF_FEATURE_REPORT_SFP_DATA 0x00000800 +#define FSF_FEATURE_FC_SECURITY 0x00001000#define FSF_FEATURE_DIF_PROT_TYPE1 0x00010000#define FSF_FEATURE_DIX_PROT_TCPIP 0x00020000
@@ -174,6 +175,11 @@/* option */ #define FSF_OPEN_LUN_SUPPRESS_BOXING 0x00000001 +/* FC security algorithms */ +#define FSF_FC_SECURITY_AUTH 0x00000001 +#define FSF_FC_SECURITY_ENC_FCSP2 0x00000002 +#define FSF_FC_SECURITY_ENC_ERAS 0x00000004 +struct fsf_queue_designator {u8 cssid;u8 chpid;
@@ -338,7 +344,8 @@ struct fsf_qtcb_bottom_support {u8 res3[3 ];u8 timeout;u32 lun_access_info; -u8 res4[180 ]; +u32 connection_info; +u8 res4[176 ];u32 els1_length;u32 els2_length;u32 req_buf_length;
@@ -426,7 +433,8 @@ struct fsf_qtcb_bottom_port { u16 port_tx_type :4; }; } sfp_flags; -u8 res3[240 ]; +u32 fc_security_algorithms; +u8 res3[236 ]; } __attribute__ ((packed)); union fsf_qtcb_bottom {
drivers/s390/scsi/zfcp_sysfs.c +69 -1
100 lines not on this page · raw message
Signature · 1 line
2.17.1
PATCH 10/10 zfcp: log FC Endpoint Security errors
In reply to Steffen MaierFrom: Jens Remus <[email protected]>
Log any FC Endpoint Security errors to the kernel ring buffer with rate- limiting.
--- drivers/s390/scsi/zfcp_fsf.c | 62 ++++++++++++++++++++++++++++++++++++ drivers/s390/scsi/zfcp_fsf.h | 8 +++++ 2 files changed, 70 insertions(+)
drivers/s390/scsi/zfcp_fsf.c +62 -0
@@ -1647,6 +1647,62 @@ static void zfcp_fsf_log_port_fc_security(struct zfcp_port *port, port->connection_info_old = port->connection_info; } +static void zfcp_fsf_log_security_error (const struct device *dev,u32 fsf_sqw0, +u64 wwpn) +{ +switch (fsf_sqw0) { + +/* +* Open Port command error codes +*/ + +case FSF_SQ_SECURITY_REQUIRED : +dev_warn_ratelimited (dev, +"FC Endpoint Security error: FC security is required but not supported or configured on remote port 0x%016llx\n" , + wwpn); +break ; +case FSF_SQ_SECURITY_TIMEOUT : +dev_warn_ratelimited (dev, +"FC Endpoint Security error: a timeout prevented opening remote port 0x%016llx\n" , + wwpn); +break ; +case FSF_SQ_SECURITY_KM_UNAVAILABLE : +dev_warn_ratelimited (dev, +"FC Endpoint Security error: opening remote port 0x%016llx failed because local and external key manager cannot communicate\n" , + wwpn); +break ; +case FSF_SQ_SECURITY_RKM_UNAVAILABLE : +dev_warn_ratelimited (dev, +"FC Endpoint Security error: opening remote port 0x%016llx failed because it cannot communicate with the external key manager\n" , + wwpn); +break ; +case FSF_SQ_SECURITY_AUTH_FAILURE : +dev_warn_ratelimited (dev, +"FC Endpoint Security error: the device could not verify the identity of remote port 0x%016llx\n" , + wwpn); +break ; + +/* +* Send FCP command error codes +*/ + +case FSF_SQ_SECURITY_ENC_FAILURE : +dev_warn_ratelimited (dev, +"FC Endpoint Security error: FC connection to remote port 0x%016llx closed because encryption broke down\n" , + wwpn); +break ; + +/* +* Unknown error codes +*/ + +default : +dev_warn_ratelimited (dev, +"FC Endpoint Security error: the device issued an unknown error code 0x%08x related to the FC connection to remote port 0x%016llx\n" , + fsf_sqw0, wwpn); + } +} +static void zfcp_fsf_open_port_handler (struct zfcp_fsf_req *req) {struct zfcp_adapter *adapter = req->adapter;
@@ -1671,6 +1727,9 @@ static void zfcp_fsf_open_port_handler(struct zfcp_fsf_req *req) req->status |=ZFCP_STATUS_FSFREQ_ERROR ;break ;case FSF_SECURITY_ERROR : +zfcp_fsf_log_security_error (&req->adapter->ccw_device->dev, + header->fsf_status_qual.word[0 ], + port->wwpn); req->status |=ZFCP_STATUS_FSFREQ_ERROR ;break ;case FSF_ADAPTER_STATUS_AVAILABLE :
@@ -2404,6 +2463,9 @@ static void zfcp_fsf_fcp_handler_common(struct zfcp_fsf_req *req, req->status |=ZFCP_STATUS_FSFREQ_ERROR ;break ;case FSF_SECURITY_ERROR : +zfcp_fsf_log_security_error (&req->adapter->ccw_device->dev, + header->fsf_status_qual.word[0 ], + zfcp_sdev->port->wwpn);zfcp_erp_port_forced_reopen (zfcp_sdev->port,0 ,"fssfch7" ); req->status |=ZFCP_STATUS_FSFREQ_ERROR ;break ;
drivers/s390/scsi/zfcp_fsf.h +8 -0
@@ -111,6 +111,14 @@#define FSF_PSQ_LINK_MODE_TABLE_CURRUPTED 0x00004000#define FSF_PSQ_LINK_NO_WWPN_ASSIGNMENT 0x00008000 +/* FSF status qualifier, security error */ +#define FSF_SQ_SECURITY_REQUIRED 0x00000001 +#define FSF_SQ_SECURITY_TIMEOUT 0x00000002 +#define FSF_SQ_SECURITY_KM_UNAVAILABLE 0x00000003 +#define FSF_SQ_SECURITY_RKM_UNAVAILABLE 0x00000004 +#define FSF_SQ_SECURITY_AUTH_FAILURE 0x00000005 +#define FSF_SQ_SECURITY_ENC_FAILURE 0x00000010 +/* payload size in status read buffer */ #define FSF_STATUS_READ_PAYLOAD_SIZE 4032
Signature · 1 line
2.17.1
PATCH 9/10 zfcp: enhance handling of FC Endpoint Security errors
In reply to Steffen MaierFrom: Jens Remus <[email protected]>
Enable for explicit FCP channel FC Endpoint Security error reporting and handle any FSF security errors according to specification. Take the following recovery actions when a FSF_SECURITY_ERROR is reported for the specified FSF commands:
- Open Port: Retry the command if possible
- Send FCP : Physically close the remote port and reopen
For Open Port the command status is set to error, which triggers a retry. For Send FCP the command status is set to error and recovery is triggered to physically reopen the remote port.
--- drivers/s390/scsi/zfcp_fsf.c | 13 +++++++++++-- drivers/s390/scsi/zfcp_fsf.h | 1 + 2 files changed, 12 insertions(+), 2 deletions(-)
drivers/s390/scsi/zfcp_fsf.c +11 -2
@@ -1405,7 +1405,8 @@ int zfcp_fsf_exchange_config_data(struct zfcp_erp_action *erp_action) req->qtcb->bottom.config.feature_selection =FSF_FEATURE_NOTIFICATION_LOST |FSF_FEATURE_UPDATE_ALERT | -FSF_FEATURE_REQUEST_SFP_DATA ; +FSF_FEATURE_REQUEST_SFP_DATA | +FSF_FEATURE_FC_SECURITY ; req->erp_action = erp_action; req->handler = zfcp_fsf_exchange_config_data_handler; erp_action->fsf_req_id = req->req_id;
@@ -1459,7 +1460,8 @@ int zfcp_fsf_exchange_config_data_sync(struct zfcp_qdio *qdio, req->qtcb->bottom.config.feature_selection =FSF_FEATURE_NOTIFICATION_LOST |FSF_FEATURE_UPDATE_ALERT | -FSF_FEATURE_REQUEST_SFP_DATA ; +FSF_FEATURE_REQUEST_SFP_DATA | +FSF_FEATURE_FC_SECURITY ;if (data) req->data = data;
@@ -1668,6 +1670,9 @@ static void zfcp_fsf_open_port_handler(struct zfcp_fsf_req *req) ZFCP_STATUS_COMMON_ERP_FAILED); req->status |=ZFCP_STATUS_FSFREQ_ERROR ;break ; +case FSF_SECURITY_ERROR : + req->status |=ZFCP_STATUS_FSFREQ_ERROR ; +break ;case FSF_ADAPTER_STATUS_AVAILABLE :switch (header->fsf_status_qual.word[0 ]) {case FSF_SQ_INVOKE_LINK_TEST_PROCEDURE :
@@ -2398,6 +2403,10 @@ static void zfcp_fsf_fcp_handler_common(struct zfcp_fsf_req *req,zfcp_fc_test_link (zfcp_sdev->port); req->status |=ZFCP_STATUS_FSFREQ_ERROR ;break ; +case FSF_SECURITY_ERROR : +zfcp_erp_port_forced_reopen (zfcp_sdev->port,0 ,"fssfch7" ); + req->status |=ZFCP_STATUS_FSFREQ_ERROR ; +break ; } }
drivers/s390/scsi/zfcp_fsf.h +1 -0
@@ -78,6 +78,7 @@#define FSF_BLOCK_GUARD_CHECK_FAILURE 0x00000081#define FSF_APP_TAG_CHECK_FAILURE 0x00000082#define FSF_REF_TAG_CHECK_FAILURE 0x00000083 +#define FSF_SECURITY_ERROR 0x00000090#define FSF_ADAPTER_STATUS_AVAILABLE 0x000000AD#define FSF_FCP_RSP_AVAILABLE 0x000000AF#define FSF_UNKNOWN_COMMAND 0x000000E2
Signature · 1 line
2.17.1
Martin K. Petersen
AppliedSteffen,
Quoted 1 line
one small zfcp fix and 2 features for v5.7.
Applied to 5.7/scsi-queue, thank you!
Signature · 1 line
Martin K. Petersen Oracle Linux Engineering