[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Make sure we don't do cleanup while holding state_lock in op...

2017-10-31 Thread GerritHub
>From Frank Filz : Frank Filz has uploaded this change for review. ( https://review.gerrithub.io/385167 Change subject: Make sure we don't do cleanup while holding state_lock in open4_ex .. Make sure

[Nfs-ganesha-devel] Backport list for 2.5.4

2017-10-31 Thread Daniel Gryniewicz
Here's the set of commits that downstream Ceph needs. Gluster can also use the non-Ceph related ones. Note, these are oldest first, not newest first. Daniel commit b862fe360b2a0f1b1d9d5d6a8b91f1550b66b269 Author: Gui Hecheng AuthorDate: Thu Mar 30

[Nfs-ganesha-devel] NFS v4.1 close

2017-10-31 Thread Frank Filz
Trond pointed this out for knfsd... 18.2.4. IMPLEMENTATION Even though CLOSE returns a stateid, this stateid is not useful to the client and should be treated as deprecated. CLOSE "shuts down" the state associated with all OPENs for the file by a single openowner. As noted above, CLOSE will

Re: [Nfs-ganesha-devel] Ganesha 2.3 and 2.5 - crash in free_nfs_request

2017-10-31 Thread Daniel Gryniewicz
This sounds like a use-after-free. That memory is either poisoned by the allocator, or re-allocated and used by something that memset() it. You can try running under valgrind, if it's fast enough, or you can try backporting the ASAN additions from these commits:

Re: [Nfs-ganesha-devel] Ganesha 2.3 and 2.5 - crash in free_nfs_request

2017-10-31 Thread Sachin Punadikar
William, You are right, gsh_calloc is getting invoked (even for 2.3 code). Interestingly for the core we got in testing, has almost all the fields filled with 0xFF. So wondering is it something to do with underneath glibc or RHEL in general. Here is the gdb o/p indicating the same. (gdb) p

Re: [Nfs-ganesha-devel] UID and GID mapping

2017-10-31 Thread Nitesh Sharma
Hello, root@d00-0c-29-05-b8-ca:~ # rpm -qa | grep nfs-ganesha nfs-ganesha-ceph-2.4.1+git.1478770945.6b4788a-1.4.x86_64 nfs-ganesha-2.4.1+git.1478770945.6b4788a-1.4.x86_64 That the version getting used. Thanks in advance. On Mon, Oct 30, 2017 at 9:43 PM, William Allen Simpson <

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Fix attempt to acquire content_lock twice

2017-10-31 Thread GerritHub
>From Malahal : Malahal has uploaded this change for review. ( https://review.gerrithub.io/385104 Change subject: Fix attempt to acquire content_lock twice .. Fix attempt to acquire content_lock twice

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: FSAL_GLUSTER: Fix memory leak while reading dirents

2017-10-31 Thread GerritHub
>From Soumya : Soumya has uploaded this change for review. ( https://review.gerrithub.io/385085 Change subject: FSAL_GLUSTER: Fix memory leak while reading dirents .. FSAL_GLUSTER: Fix memory leak while

Re: [Nfs-ganesha-devel] UID and GID mapping

2017-10-31 Thread Soumya Koduri
Anonymous_uid & Anonymous_gid options can used in EXPORT {} block to set anonuid/anongid [1] Thanks, Soumya [1] https://github.com/nfs-ganesha/nfs-ganesha/blob/next/src/config_samples/config.txt#L210 On 10/30/2017 09:43 PM, William Allen Simpson wrote: On 10/30/17 3:56 AM, Nitesh Sharma