[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: WIP: Fix nlm client refcount going up from zero

>From Malahal : Malahal has uploaded a new change for review. ( https://review.gerrithub.io/348993 Change subject: WIP: Fix nlm client refcount going up from zero .. WIP: Fix nlm client refcount going up

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Fix state_test calling LogLock when there is no conflict

>From Malahal : Malahal has uploaded a new change for review. ( https://review.gerrithub.io/348994 Change subject: Fix state_test calling LogLock when there is no conflict .. Fix state_test calling LogLock

Re: [Nfs-ganesha-devel] Dirent invalidation on up call

> er, oh noes... The problem I think I see is that the directory never gets cleaned out in this case... I get that we may not want to dispose of the dirents on the upcall thread, but we should dispose of them the next time we do a lookup or readdir... Everything else that invalidates a

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: [nlm_Test] Reference mioght be used un-initialized.

>From Swen Schillig : Swen Schillig has uploaded a new change for review. ( https://review.gerrithub.io/348794 Change subject: [nlm_Test] Reference mioght be used un-initialized. .. [nlm_Test] Reference

Re: [Nfs-ganesha-devel] reg. FSAL_ACE_PERM_WRITE_DATA check in fsal_check_setattr_perms

Frank, I have subscribed to the list. Apologies for any inconvenience caused. > This wouldn't actually help since the call to test_access just winds up in > fsal_test_access which isn't going to know about your special super user. > All Ganesha is doing here is not making a test_access call that

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: FSAL_PROXY (support_ex without state) : pxy_setattr2

>From Patrice LUCAS : Patrice LUCAS has uploaded a new change for review. ( https://review.gerrithub.io/348756 Change subject: FSAL_PROXY (support_ex without state) : pxy_setattr2 .. FSAL_PROXY

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Fixing a deadlock between reaper thread and setclientid

>From Sriram Patil : Sriram Patil has uploaded a new change for review. ( https://review.gerrithub.io/348712 Change subject: Fixing a deadlock between reaper thread and setclientid .. Fixing a

Re: [Nfs-ganesha-devel] Dirent invalidation on up call

er, oh noes... Matt - Original Message - > From: "Frank Filz" > To: nfs-ganesha-devel@lists.sourceforge.net > Sent: Wednesday, February 15, 2017 7:43:40 PM > Subject: [Nfs-ganesha-devel] Dirent invalidation on up call > > I'm looking at when dirents are

Re: [Nfs-ganesha-devel] reg. FSAL_ACE_PERM_WRITE_DATA check in fsal_check_setattr_perms

> Frank, > > I have subscribed to the list. Apologies for any inconvenience caused. > > > This wouldn't actually help since the call to test_access just winds > > up in fsal_test_access which isn't going to know about your special super > user. > > All Ganesha is doing here is not making a

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Pull up ntirpc #39

>From : william.allen.simp...@gmail.com has uploaded a new change for review. ( https://review.gerrithub.io/348814 Change subject: Pull up ntirpc #39 .. Pull up ntirpc #39 Change-Id:

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: FSAL_PROXY (support_ex without state) : pxy_status2

>From Patrice LUCAS : Patrice LUCAS has uploaded a new change for review. ( https://review.gerrithub.io/348901 Change subject: FSAL_PROXY (support_ex without state) : pxy_status2 .. FSAL_PROXY

[Nfs-ganesha-devel] Dirent invalidation on up call

I'm looking at when dirents are invalidated, and it looks like MDCACHE_DIR_POPULATED is cleared on up call, but nothing actually cleans out the dirents... Is this an omission? Frank --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Fix SSE4_2 compile path.

>From Dylan Reid : Dylan Reid has uploaded a new change for review. ( https://review.gerrithub.io/348971 Change subject: Fix SSE4_2 compile path. .. Fix SSE4_2 compile path. A semicolon has been missing