Hi,
This is the agenda for tomorrow's community meeting for NA/EMEA timezone.
https://hackmd.io/OqZbh7gfQe6uvVUXUVKJ5g?both
On Thu, Apr 11, 2019 at 4:56 AM Amar Tumballi Suryanarayan <
atumb...@redhat.com> wrote:
> Hi All,
>
> Below is the final details of our community meeting, and I
Is this back again? The recent patches are failing regression :-\ .
On Wed, 3 Apr 2019 at 19:26, Michael Scherer wrote:
> Le mercredi 03 avril 2019 à 16:30 +0530, Atin Mukherjee a écrit :
> > On Wed, Apr 3, 2019 at 11:56 AM Jiffin Thottan
> > wrote:
> >
> > > Hi,
> > >
> > >
The above test is failing all day today because of rpc-statd going into
inactive state on builders.
I've been trying to enable this service going in dead state after every
run.
1. rpcbind and rpcbind.socket is running on builders
2. ipv6 is disabled.
3. nfs-server is also working fine
4.
The Gluster community is pleased to announce the release of Gluster
6.1 (packages available at [1]).
Release notes for the release can be found at [2].
Major changes, features and limitations addressed in this release:
None
Thanks,
Gluster community
[1] Packages for 6.1:
Ok, I am clear now.
I’ve added ssl_free in socket reset and socket finish function, though
glusterfsd memory leak is not that much, still it is leaking, from source code
I can not find anything else,
Could you help to check if this issue exists in your env? If not I may have a
try to merge your
According to BIO_new_socket() man page ...
*If the close flag is set then the socket is shut down and closed when the
BIO is freed.*
For Gluster to have more control over the socket shutdown, the BIO_NOCLOSE
flag is set. Otherwise, SSL takes control of socket shutdown whenever BIO
is freed.
Ok ,another question, why priv->ssl_sbio = BIO_new_socket(priv->sock,
BIO_NOCLOSE); use NOCLOSE mode instead of BIO_CLOSE?
cynthia
From: Milind Changire
Sent: Monday, April 22, 2019 2:21 PM
To: Zhou, Cynthia (NSB - CN/Hangzhou)
Cc: Atin Mukherjee ; gluster-devel@gluster.org
Subject: Re:
Looks like using BIO_free() is not right. Here's what the SSL_set_bio() man
page says ...
SSL_set_bio() is similar to SSL_set0_rbio() and SSL_set0_wbio() except that
it connects both the rbio and the wbio at the same time, and *transfers the
ownership of rbio and wbio to ssl* according to the
I do some google. Seems it is not needed to call BIO_free, SSL_free will free
bio.
https://groups.google.com/forum/#!topic/mailing.openssl.users/8i9cRQGlfDM
From: Milind Changire
Sent: Monday, April 22, 2019 1:35 PM
To: Zhou, Cynthia (NSB - CN/Hangzhou)
Cc: Atin Mukherjee ;
I tried to print priv->ssl_sbio after SSL_free() find this pointer is not null,
so I add free ssl_sbio with BIO_free, however this cause glusterfd coredump
(gdb) bt
#0 0x7f3047867f9b in raise () from /lib64/libc.so.6
#1 0x7f3047869351 in abort () from /lib64/libc.so.6
#2
10 matches
Mail list logo
