Bug 1508036 - Address lstat usage in glusterd-snapshot.c code
Summary: Address lstat usage in glusterd-snapshot.c code
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Shyamsundar
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1508039
TreeView+ depends on / blocked
 
Reported: 2017-10-31 17:51 UTC by Shyamsundar
Modified: 2017-12-08 16:46 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.10.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1508039 (view as bug list)
Environment:
Last Closed: 2017-12-08 16:46:32 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Shyamsundar 2017-10-31 17:51:06 UTC 
Description of problem:

See devel discussion: http://lists.gluster.org/pipermail/gluster-devel/2017-October/053861.html

Needs a backport of: https://review.gluster.org/#/c/16820/
Comment 1 Worker Ant 2017-10-31 17:55:33 UTC 
REVIEW: https://review.gluster.org/18602 (glusterd: use sys_lstat instead of lstat) posted (#1) for review on release-3.10 by Shyamsundar Ranganathan
Comment 2 Atin Mukherjee 2017-11-06 03:40:10 UTC 
https://review.gluster.org/18602 is merged but gerrit didn't update the bug with the commit.
Comment 3 Shyamsundar 2017-12-08 16:46:32 UTC 
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.8, please open a new bug report.

glusterfs-3.10.8 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-December/000086.html
[2] https://www.gluster.org/pipermail/gluster-users/
Note You need to log in before you can comment on or make changes to this bug.