marker: Fix inode value in loc, in setxattr fop

2016-11-22T05:44:23+00:00

Backport of http://review.gluster.org/15826

On recieving a rename fop, marker_rename() stores the,
oldloc and newloc in its 'local' struct, once the rename
is done, the xtime marker(last updated time) is set on
the file, but sending a setxattr fop. When upcall
receives the setxattr fop, the loc->inode is NULL and
it crashes. The loc->inode can be NULL only in one valid
case, i.e. in rename case where the inode of new loc
can be NULL. Hence, marker should have filled the inode
of the new_loc before issuing a setxattr.

> Reviewed-on: http://review.gluster.org/15826
> NetBSD-regression: NetBSD Build System 
> CentOS-regression: Gluster Build System 
> Reviewed-by: Kotresh HR 
> Smoke: Gluster Build System 
> Reviewed-by: Rajesh Joseph 
(cherry picked from commit 46e5466850311ee69e6ae9a11c2bba2aabadd5de)

Change-Id: Id638f678c3daaf4a5c29b970b58929d377ae8977
BUG: 1396419
Signed-off-by: Poornima G 
Reviewed-on: http://review.gluster.org/15879
Reviewed-by: Rajesh Joseph 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System

Upcall/cache-invalidation: Ignore fops with frame->root->client not set

2015-06-09T18:49:04+00:00

Server-side internally generated fops like 'quota/marker' will
not have any client associated with the frame. Hence we need a
check for clients to be valid before processing for upcall cache
invalidation. Also fixed an issue with initializing reaper-thread.

Added a testcase to test the fix.

Change-Id: If7419b98aca383f4b80711c10fef2e0b32498c57
BUG: 1221941
Signed-off-by: Soumya Koduri 
Reviewed-on: http://review.gluster.org/10909
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: jiffin tony Thottan 
Reviewed-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/11141
Tested-by: NetBSD Build System

glusterfs.git/tests/bugs/upcall, branch v3.7.20

marker: Fix inode value in loc, in setxattr fop

Upcall/cache-invalidation: Ignore fops with frame->root->client not set