On 08/10/2010 02:09 PM, Eddie Wai wrote:
In the case when an ep_connect request is interrupted due to route request stall, if the iSCSI daemon is terminated by the user, the chip will be left in a state which will not get cleaned up upon module removal. Upon module reload, when the same context id is used for a new connection, chip panic would occur. This patch adds chip cleanup in the module removal path. Signed-off-by: Eddie Wai<eddie.wai@xxxxxxxxxxxx> Acked-by: Benjamin Li<benli@xxxxxxxxxxxx> --- drivers/scsi/bnx2i/bnx2i_init.c | 53 +++++++++++++++++++++++-------------- drivers/scsi/bnx2i/bnx2i_iscsi.c | 3 ++ 2 files changed, 36 insertions(+), 20 deletions(-) diff --git a/drivers/scsi/bnx2i/bnx2i_init.c b/drivers/scsi/bnx2i/bnx2i_init.c index a796f56..99b861b 100644 --- a/drivers/scsi/bnx2i/bnx2i_init.c +++ b/drivers/scsi/bnx2i/bnx2i_init.c @@ -167,6 +167,37 @@ void bnx2i_start(void *handle) /** + * bnx2i_chip_cleanup - local routine to handle chip cleanup
For docbook comments you need the argument info @hba: driver's hba struct -- 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
