[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <653eaa6f-4e85-43af-a13b-906e34a2e517@oracle.com>
Date: Thu, 17 Jul 2025 15:01:11 -0500
From: Mike Christie <michael.christie@...cle.com>
To: Li Lingfeng <lilingfeng3@...wei.com>, lduncan@...e.com, cleech@...hat.com,
njavali@...vell.com, mrangankar@...vell.com,
GR-QLogic-Storage-Upstream@...vell.com, martin.petersen@...cle.com,
jejb@...ux.ibm.com, James.Bottomley@...senPartnership.com
Cc: open-iscsi@...glegroups.com, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org, yukuai1@...weicloud.com,
houtao1@...wei.com, yi.zhang@...wei.com, yangerkun@...wei.com,
chengzhihao1@...wei.com, lilingfeng@...weicloud.com
Subject: Re: [PATCH] Revert "scsi: iscsi: Fix HW conn removal use after free"
On 7/15/25 2:39 AM, Li Lingfeng wrote:
> This reverts commit c577ab7ba5f3bf9062db8a58b6e89d4fe370447e.
>
> The invocation of iscsi_put_conn() in iscsi_iter_destory_conn_fn() is used
> to free the initial reference counter of iscsi_cls_conn.
> For non-qla4xxx cases, the ->destroy_conn() callback (e.g.,
> iscsi_conn_teardown) will call iscsi_remove_conn() and iscsi_put_conn() to
> remove the connection from the children list of session and free the
> connection at last.
> However for qla4xxx, it is not the case. The ->destroy_conn() callback
> of qla4xxx will keep the connection in the session conn_list and doesn't
> use iscsi_put_conn() to free the initial reference counter. Therefore,
> it seems necessary to keep the iscsi_put_conn() in the
> iscsi_iter_destroy_conn_fn(), otherwise, there will be memory leak
> problem.
>
I must have thought we did a unregister instead of remove for
some reason. Thanks for catching this.
Reviewed-by: Mike Christie <michael.christie@...cle.com>
Powered by blists - more mailing lists