The following series implements bug fixes for libfc,
libfcoe and fcoe.
Included in this series is the patch:
scsi: use list_move() instead of list_del()/list_add() combination
It touches other SCSI files outside of libfc, libfcoe
and fcoe. I just collected it because it touched fcoe. If I
should resend without it, please let me know.
Also, I was unable to re-test all of these patches with 39-rc1.
A driver bug is blocking me. All of the patches were reviewed
and tested before being applied to my tree, but usually I re-test
each patch just before sending to linux-scsi. I wanted to get
these patches out before LSF and don't have time to debug the
driver bug right now. I can test again after LSF if you'd like
to delay applying the patches until then. Even though I am
blocked in my re-test I have high confidence in these patches
otherwise I wouldn't send them out.
---
Kirill A. Shutemov (1):
scsi: use list_move() instead of list_del()/list_add() combination
Robert Love (3):
libfcoe: Remove mutex_trylock/restart_syscall checks
fcoe: Remove mutex_trylock/restart_syscall checks
libfc: Move host_lock usage into ramp_up/down routines
Vasu Dev (3):
libfc: remove duplicate ema_list init
libfc: rec tov value and REC_TOV_CONST units usages is incorrect
fcoe: have fcoe log off and lport destroy before ndo_fcoe_disable
Yi Zou (4):
fcoe: remove unnecessary module state check
libfcoe: clean up netdev mapping properly when the transport goes away
libfcoe: fix possible buffer overflow in fcoe_transport_show
libfcoe: fix wrong comment in fcoe_transport_detach
drivers/scsi/esp_scsi.c | 6 -
drivers/scsi/fcoe/fcoe.c | 202 +++++++++++-------------------------
drivers/scsi/fcoe/fcoe_ctlr.c | 6 -
drivers/scsi/fcoe/fcoe_transport.c | 56 +++++-----
drivers/scsi/libfc/fc_fcp.c | 57 ++++------
drivers/scsi/libfc/fc_lport.c | 1
drivers/scsi/scsi_tgt_lib.c | 6 -
7 files changed, 122 insertions(+), 212 deletions(-)
--
Thanks, //Rob
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
