On 05/06/2010 03:24 AM, Or Gerlitz wrote:
Mike Christie wrote:
I agree on it being a bug, but do you remember why that was added to
iscsi_iser_conn_destroy originally?
I later moved it to iser_conn_release in commit
b40977d95fb3a1898ace6a7d97e4ed1a33a440a4)
but I think Erez had added that null
Mike Christie wrote:
> I agree on it being a bug, but do you remember why that was added to
> iscsi_iser_conn_destroy originally?
> I later moved it to iser_conn_release in commit
> b40977d95fb3a1898ace6a7d97e4ed1a33a440a4)
> but I think Erez had added that null and some checks for it being null
Mike Christie wrote:
> Or Gerlitz wrote:
>> since iscsi connection objects are recycled, on the time the transport
>> connection
>> (e.g iser's ib connection) is released it is illegal to touch the iscsi
>> connection tied to the
>> transport back-pointer, as it may already point to a differen
On 05/05/2010 09:30 AM, Or Gerlitz wrote:
iscsi connection object life cycle includes binding and unbinding
(conn_stop) to/from the iscsi transport connection object. Since
iscsi connection objects are recycled, on the time the transport
connection (e.g iser's ib connection) is released it is ill
iscsi connection object life cycle includes binding and unbinding
(conn_stop) to/from the iscsi transport connection object. Since
iscsi connection objects are recycled, on the time the transport
connection (e.g iser's ib connection) is released it is illegal
to touch the iscsi connection tied to t