Hi,
I was attempting to fix a class of "Insecure data handling" defects in
coverity around GF_FREE accessing tainted strings. Below is a short
writeup of the same (pasted into the notes for each issue as well).
Notifying the list of the same.
(attempted annotation) Fix: https://review.gluster.org
On Tue, Nov 6, 2018 at 7:53 AM Atin Mukherjee
wrote:
> new defects introduced in posix xlator.
>
>
The new defect is in the features/locks xlator. I have sent a patch to
address that.
Thanks,
Vijay
-- Forwarded message -
> From:
> Date: Tue, Nov 6, 2018 at 8:44 PM
> Subject: Ne
On Tue, Nov 6, 2018, 5:51 PM Atin Mukherjee new defects introduced in posix xlator.
>
The other one in iobuf.c, is mine.
Sent a patch to fix.
Y.
> -- Forwarded message -
> From:
> Date: Tue, Nov 6, 2018 at 8:44 PM
> Subject: New Defects reported by Coverity Scan for gluster/glu
Hi,
With release-5 out of the door, it is time to start some activities for
release-6.
## Scope
It is time to collect and determine scope for the release, so as usual,
please send in features/enhancements that you are working towards
reaching maturity for this release to the devel list, and mark/
new defects introduced in posix xlator.
-- Forwarded message -
From:
Date: Tue, Nov 6, 2018 at 8:44 PM
Subject: New Defects reported by Coverity Scan for gluster/glusterfs
Hi,
Please find the latest report on new defect(s) introduced to
gluster/glusterfs found with Coverity Scan
Le mardi 06 novembre 2018 à 15:30 +0100, Michael Scherer a écrit :
> Hi,
>
> I just got paged for a issue regarding gerrit and jenkins, so I am
> looking at it. I do not have much info now, but just letting people
> know that we are on it.
Network is back, i am discussing with our network team to
Hi,
I just got paged for a issue regarding gerrit and jenkins, so I am
looking at it. I do not have much info now, but just letting people
know that we are on it.
--
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS
signature.asc
Description: This is a digitally signed me
On 11/05/2018 10:56 PM, Raghavendra Gowdappa wrote:
> All,
>
> There is a patch [1] from Kotresh, which makes ctime generator as
> default in stack. Currently ctime generator is being recommended only
> for usecases where ctime is important (like for Elasticsearch). However,
> a reliable (c)(m)tim
We have enabled GD2 smoke results as a mandatory vote in glusterfs smoke
since yesterday through BZ [1], however we just started seeing GD2 smoke
failing which means glusterfs smoke on all the patches will not go through
at this moment.. GD2 dev is currently working on it and trying to rectify
the
