[Bugs] [Bug 1636246] New: [GSS] SMBD crashes when streams_attr VFS is used with Gluster VFS

Thu Oct 4 20:06:21 UTC 2018

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

            Bug ID: 1636246
           Summary: [GSS] SMBD crashes when streams_attr VFS is used with
                    Gluster VFS
           Product: Red Hat Gluster Storage
           Version: 3.4
         Component: libgfapi
          Severity: medium
          Assignee: pgurusid at redhat.com
          Reporter: ccalhoun at redhat.com
        QA Contact: vdas at redhat.com
                CC: bugs at gluster.org, dan.ragnar at amra.se,
                    jthottan at redhat.com, rhs-bugs at redhat.com,
                    ryan at magenta.tv, sankarshan at redhat.com,
                    skoduri at redhat.com, storage-qa-internal at redhat.com
        Depends On: 1602824

+++ This bug was initially created as a clone of Bug #1602824 +++

Description of problem:
SMBD thread panics when streams_xattr is used before gluster VFS

Version-Release number of selected component (if applicable):
Samba (tested with): 4.7.7, 4.7.8, 4.8.3
Gluster: 3.12.11

How reproducible:
Can reproduce everytime

Steps to Reproduce:
1.In Samba, set log level to 1
2.In Samba, create a share with the following:

[share]
vfs objects = fruit streams_xattr glusterfs
guest ok = yes
read only = no
glusterfs:volume = myVol01
path =  "/data/share01"

3.Restart Samba service
4.Tail the Samba log file at /var/log/samba
5.Connect to the share via an OS X client (Tested with 10.13.4)
6. Browse share at finder level

Actual results:
SMBD thread panics and kills clients connection

Expected results:
Share lists normally 

Additional info:
Don't happen from a Windows system

---

In support case 02194103:

When Samba is configured with vfs_glusterfs and vfs_fruit (and streams_xattr),
it crashes when it is accessed from a Mac OS high sierra machine. It crashes
with the following log ouput (log.smbd):

[2018/10/01 18:59:24.940519,  0]
../source3/modules/vfs_glusterfs.c:371(vfs_gluster_connect)
  vfs_gluster_connect: staging: Initialized volume from servers localhost
[2018/10/01 18:59:24.951221,  0] ../lib/util/fault.c:78(fault_report)
  ===============================================================
[2018/10/01 18:59:24.951261,  0] ../lib/util/fault.c:79(fault_report)
  INTERNAL ERROR: Signal 11 in pid 54093 (4.7.5)
  Please read the Trouble-Shooting section of the Samba HOWTO
[2018/10/01 18:59:24.951286,  0] ../lib/util/fault.c:81(fault_report)
  ===============================================================
[2018/10/01 18:59:24.951304,  0] ../source3/lib/util.c:815(smb_panic_s3)
  PANIC (pid 54093): internal error
[2018/10/01 18:59:24.951821,  0] ../source3/lib/util.c:926(log_stack_trace)
  BACKTRACE: 28 stack frames:
   #0 /lib64/libsmbconf.so.0(log_stack_trace+0x1a) [0x7f0bd3acfd0a]
   #1 /lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f0bd3acfde0]
   #2 /lib64/libsamba-util.so.0(smb_panic+0x2f) [0x7f0bd5bcab8f]
   #3 /lib64/libsamba-util.so.0(+0x24da6) [0x7f0bd5bcada6]
   #4 /lib64/libpthread.so.0(+0xf680) [0x7f0bd6032680]
   #5 /usr/lib64/samba/vfs/glusterfs.so(+0x4af2) [0x7f0bb62baaf2]
   #6 /usr/lib64/samba/libsmbd-base-samba4.so(fd_close+0x40) [0x7f0bd57b5a90]
   #7 /usr/lib64/samba/libsmbd-base-samba4.so(close_file+0x5e6)
[0x7f0bd57be756]
   #8 /usr/lib64/samba/libsmbd-base-samba4.so(+0x1c8013) [0x7f0bd57f6013]
   #9
/usr/lib64/samba/libsmbd-base-samba4.so(smbd_smb2_request_process_close+0x17d)
[0x7f0bd57f685d]
   #10
/usr/lib64/samba/libsmbd-base-samba4.so(smbd_smb2_request_dispatch+0x17b3)
[0x7f0bd57ea8b3]
   #11
/usr/lib64/samba/libsmbd-base-samba4.so(smbd_smb2_request_dispatch_immediate+0x75)
[0x7f0bd57ebba5]
   #12 /lib64/libtevent.so.0(tevent_common_loop_immediate+0xda)
[0x7f0bd26e696a]
   #13 /lib64/libtevent.so.0(+0xa54d) [0x7f0bd26eb54d]
   #14 /lib64/libtevent.so.0(+0x8b57) [0x7f0bd26e9b57]
   #15 /lib64/libtevent.so.0(_tevent_loop_once+0x9d) [0x7f0bd26e5f7d]
   #16 /lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7f0bd26e61ab]
   #17 /lib64/libtevent.so.0(+0x8af7) [0x7f0bd26e9af7]
   #18 /usr/lib64/samba/libsmbd-base-samba4.so(smbd_process+0x6e4)
[0x7f0bd57da074]
   #19 /usr/sbin/smbd(+0xd1d4) [0x56443f30c1d4]
   #20 /lib64/libtevent.so.0(+0xa78b) [0x7f0bd26eb78b]
   #21 /lib64/libtevent.so.0(+0x8b57) [0x7f0bd26e9b57]
   #22 /lib64/libtevent.so.0(_tevent_loop_once+0x9d) [0x7f0bd26e5f7d]
   #23 /lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7f0bd26e61ab]
   #24 /lib64/libtevent.so.0(+0x8af7) [0x7f0bd26e9af7]
   #25 /usr/sbin/smbd(main+0x1afe) [0x56443f30725e]
   #26 /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f0bd21273d5]
   #27 /usr/sbin/smbd(+0x8571) [0x56443f307571]
[2018/10/01 18:59:24.952052,  0] ../source3/lib/dumpcore.c:318(dump_core)
  coredump is handled by helper binary specified at
/proc/sys/kernel/core_pattern[2018/10/01 18:59:25.083396,  0]
../source3/modules/vfs_glusterfs.c:371(vfs_gluster_connect)

If vfs_glusterfs is removed and the samba path is pointed to a fuse mount of
the volume, the problem is not shown. The fuse mount way, however, is a lot
slower... Is there certain conditions/configurations when this is known to not
work?

Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1602824
[Bug 1602824] SMBD crashes when streams_attr VFS is used with Gluster VFS
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=b0gQLHQlrF&a=cc_unsubscribe