[Bugs] [Bug 1178020] New: dict_get() called with dict=NULL in xlators/nfs/server/src/acl3.c:acl3_getacl_cbk

bugzilla at redhat.com bugzilla at redhat.com
Thu Jan 1 13:35:35 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1178020

            Bug ID: 1178020
           Summary: dict_get() called with dict=NULL in
                    xlators/nfs/server/src/acl3.c:acl3_getacl_cbk
           Product: GlusterFS
           Version: mainline
         Component: nfs
          Keywords: Triaged
          Assignee: bugs at gluster.org
          Reporter: ndevos at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    mmadhusu at redhat.com



Created attachment 974960
  --> https://bugzilla.redhat.com/attachment.cgi?id=974960&action=edit
Patch that adds an additional check for dict==NULL to prevent calling
dict_get()

Description of problem:
When running the regression tests, there are many entries like this:

[2014-12-31 01:13:15.011922] I [dict.c:382:dict_get] (-->
/usr/lib64/libglusterfs.so.0(_gf_log_callingfn+0x147)[0x7f87710d5ac7] (-->
/usr/lib64/libglusterfs.so.0(dict_g
et+0x89)[0x7f87710cf049] (-->
/usr/lib64/glusterfs/3.7dev/xlator/nfs/server.so(acl3_getacl_cbk+0x75)[0x7f875f95eb55]
(--> /usr/lib64/glusterfs/3.7dev/xlator/nfs/server.
so(nfs_fop_getxattr_cbk+0x2c)[0x7f875f93222c] (-->
/usr/lib64/glusterfs/3.7dev/xlator/debug/io-stats.so(io_stats_getxattr_cbk+0xf4)[0x7f875fb97424]
))))) 0-dict: !this || key=system.posix_acl_access


Version-Release number of selected component (if applicable):
mainline (with patches from bug 1143880, but maybe without those too?)

How reproducible:
100%

Steps to Reproduce:
1. checkout the glusterfs sources
2. make -C extras/LinuxRPM glusterrpms
3. install the rpms on a test system
4. run /usr/share/glusterfs/run-tests.sh
5. tail -f /var/log/glusterfs/nfs.log

Actual results:
See those error messages.

Expected results:
No error messages.

Additional info:
I'm unsure why dict=NULL, this could use some more investigation.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list