Bug 1291259

Summary:	Upcall/Cache-Invalidation: Use parent stbuf while updating parent entry
Product:	[Community] GlusterFS	Reporter:	Soumya Koduri <skoduri>
Component:	upcall	Assignee:	Soumya Koduri <skoduri>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	rkavunga
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-16 13:50:45 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:

Description Soumya Koduri 2015-12-14 12:52:00 UTC

Description of problem:
While invalidating parent entries, use parent entry's stat structure in 
upcall_cache_invalidate () routine.

Comment 1 Vijay Bellur 2015-12-14 13:06:11 UTC

REVIEW: http://review.gluster.org/12962 (Upcall/cache-invalidation: Use parent stbuf while updating parent entry) posted (#2) for review on master by soumya k (skoduri)

Comment 2 Vijay Bellur 2016-02-09 06:55:57 UTC

REVIEW: http://review.gluster.org/12962 (Upcall/cache-invalidation: Use parent stbuf while updating parent entry) posted (#3) for review on master by soumya k (skoduri)

Comment 3 Vijay Bellur 2016-02-16 08:02:39 UTC

REVIEW: http://review.gluster.org/12962 (Upcall/cache-invalidation: Use parent stbuf while updating parent entry) posted (#4) for review on master by soumya k (skoduri)

Comment 4 Vijay Bellur 2016-02-16 08:55:59 UTC

COMMIT: http://review.gluster.org/12962 committed in master by Niels de Vos (ndevos) 
------
commit f4282bd927e2e0d826d62cf1192102382c5697b2
Author: Soumya Koduri <skoduri>
Date:   Mon Dec 14 17:52:37 2015 +0530

    Upcall/cache-invalidation: Use parent stbuf while updating parent entry
    
    For *create*  fops (CREATE, MKDIR, MKNOD), we invalidate the parent
    entry. Hence send parent attributes in the stat field.
    
    Also "UP_PARENT_DENTRY_FLAGS" has to be set only for the fops which shall
    result in two invalidations requests - one for the inode on which fop is
    being performed and another on parent entry.
    
    In case of CREATE/MKDIR/MKNOD fops, there shall be only one invalidation
    request sent, that too on parent inode. We send invalidation directly on
    parent inode's gfid. So there is no necessity to set these flags which
    when set shall endup invalidating the parent's parent entry.
    
    Change-Id: I7514ee08382081e3e060818ede497dbca26987dc
    BUG: 1291259
    Signed-off-by: Soumya Koduri <skoduri>
    Reviewed-on: http://review.gluster.org/12962
    CentOS-regression: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.com>
    Reviewed-by: Niels de Vos <ndevos>

Comment 5 Niels de Vos 2016-06-16 13:50:45 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.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