This probably went unnoticed until now.
On Mon, Apr 22, 2019 at 10:45 AM Zhou, Cynthia (NSB - CN/Hangzhou) <
cynthia.z...@nokia-sbell.com> wrote:
> Why there is no bio_free called in ssl_teardown_connection then?
>
>
>
> cynthia
>
>
>
> *From:* Milind Changire
> *Sent:* Monday, April 22, 2019
Hi,
Thanks for your quick responding!
My test env is without patch 22334, so priv->ssl_ctx is shared one. In
socket_reset there is no need to free it. but if with patch 22334, it is
absolutely needed to free priv->ssl_ctx as well.
Following is the log captured from glusterfsd side while
Ok, I will post it later.
cynthia
From: Raghavendra Gowdappa
Sent: Monday, April 22, 2019 10:09 AM
To: Zhou, Cynthia (NSB - CN/Hangzhou)
Cc: Atin Mukherjee ; gluster-devel@gluster.org
Subject: Re: [Gluster-devel] glusterfsd memory leak issue found after enable ssl
On Mon, Apr 22, 2019 at
Hi,
From my code study it seems priv->ssl_ssl is not properly released, I made a
patch and the glusterfsd memory leak is alleviated with my patch, but some
otherwhere is still leaking, I have no clue about the other leak points.
--- a/rpc/rpc-transport/socket/src/socket.c
+++
