Bug 1251454
Summary: | marker: set loc.parent if NULL | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Vijaikumar Mallikarjuna <vmallika> | |
Component: | quota | Assignee: | Vijaikumar Mallikarjuna <vmallika> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | bugs, gluster-bugs, smohan | |
Target Milestone: | --- | Keywords: | Reopened | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1251457 1257441 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-16 13:29:42 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1251457, 1257441 |
Description
Vijaikumar Mallikarjuna
2015-08-07 10:50:37 UTC
REVIEW: http://review.gluster.org/11863 (marker: don't log warning in txn if parent is NULL) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika) REVIEW: http://review.gluster.org/11863 (marker: don't log warning in txn if parent is NULL) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika) REVIEW: http://review.gluster.org/11863 (marker: fix log when loc.parent and inode gfid is NULL) posted (#3) for review on master by Vijaikumar Mallikarjuna (vmallika) REVIEW: http://review.gluster.org/11863 (marker: fix log when loc.parent and inode gfid is NULL) posted (#5) for review on master by Vijaikumar Mallikarjuna (vmallika) REVIEW: http://review.gluster.org/11863 (marker: fix log when loc.parent and inode gfid is NULL) posted (#8) for review on master by Vijaikumar Mallikarjuna (vmallika) REVIEW: http://review.gluster.org/11995 (posix: xattrop 'GF_XATTROP_GET_AND_SET' implementation) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika) REVIEW: http://review.gluster.org/11995 (posix: xattrop 'GF_XATTROP_GET_AND_SET' implementation) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika) REVIEW: http://review.gluster.org/11995 (posix: xattrop 'GF_XATTROP_GET_AND_SET' implementation) posted (#5) for review on master by Vijaikumar Mallikarjuna (vmallika) COMMIT: http://review.gluster.org/11995 committed in master by Raghavendra G (rgowdapp) ------ commit 6ad05cd4b7995a3791a9e45ce03dc31641e8d78f Author: vmallika <vmallika> Date: Mon Aug 24 13:14:59 2015 +0530 posix: xattrop 'GF_XATTROP_GET_AND_SET' implementation GF_XATTROP_GET_AND_SET stores the existing xattr value in xdata and sets the new value xattrop was reusing input xattr dict to set the results instead of creating new dict. This can be problem for server side xlators as the inout dict will have the value changed. Change-Id: I43369082e1d0090d211381181e9f3b9075b8e771 BUG: 1251454 Signed-off-by: vmallika <vmallika> Reviewed-on: http://review.gluster.org/11995 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Raghavendra G <rgowdapp> REVIEW: http://review.gluster.org/12032 (marker: preserve previous dirty flag during update txn) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika) REVIEW: http://review.gluster.org/12032 (marker: preserve previous dirty flag during update txn) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika) REVIEW: http://review.gluster.org/12032 (marker: preserve previous dirty flag during update txn) posted (#3) for review on master by Vijaikumar Mallikarjuna (vmallika) Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well. 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.8.0, please open a new bug report. glusterfs-3.8.0 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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |