[Bugs] [Bug 1602824] SMBD crashes when streams_attr VFS is used with Gluster VFS

[bugzilla at redhat.com]

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

joao.bauto at neuro.fchampalimaud.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |joao.bauto at neuro.fchampalim
                   |                            |aud.org



--- Comment #3 from joao.bauto at neuro.fchampalimaud.org ---
I'm getting this issue with Gluster 5.2 and Samba 4.8.3 however it only kills
the connection once a user begins copying data to the share.

Putting streams_xattr after glusterfs prevents the issue but its painly slow
when list a directory.

[2019/01/10 17:04:09.313042,  0] ../lib/util/fault.c:261(log_stack_trace)
  BACKTRACE: 28 stack frames:
   #0 /lib64/libsamba-util.so.0(log_stack_trace+0x1a) [0x7f8fab1e5aaa]
   #1 /lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f8fa90e0930]
   #2 /lib64/libsamba-util.so.0(smb_panic+0x2f) [0x7f8fab1e5b8f]
   #3 /lib64/libsamba-util.so.0(+0x24dc6) [0x7f8fab1e5dc6]
   #4 /lib64/libpthread.so.0(+0xf6d0) [0x7f8fab64e6d0]
   #5 /usr/lib64/samba/vfs/glusterfs.so(+0x43c3) [0x7f8f900173c3]
   #6 /usr/lib64/samba/libsmbd-base-samba4.so(is_posix_locked+0xd2)
[0x7f8faae39642]
   #7 /usr/lib64/samba/libsmbd-base-samba4.so(brl_locktest+0x184)
[0x7f8faae37174]
   #8 /usr/lib64/samba/libsmbd-base-samba4.so(strict_lock_check_default+0x7b)
[0x7f8faae3255b]
   #9
/usr/lib64/samba/libsmbd-base-samba4.so(smbd_smb2_request_process_read+0x51e)
[0x7f8faae04e1e]
   #10
/usr/lib64/samba/libsmbd-base-samba4.so(smbd_smb2_request_dispatch+0x164c)
[0x7f8faadf75bc]
   #11
/usr/lib64/samba/libsmbd-base-samba4.so(smbd_smb2_request_dispatch_immediate+0x5d)
[0x7f8faadf8a2d]
   #12 /lib64/libtevent.so.0(tevent_common_loop_immediate+0xda)
[0x7f8fa7adc9ea]
   #13 /lib64/libtevent.so.0(+0xa5fd) [0x7f8fa7ae15fd]
   #14 /lib64/libtevent.so.0(+0x8c07) [0x7f8fa7adfc07]
   #15 /lib64/libtevent.so.0(_tevent_loop_once+0x9d) [0x7f8fa7adbffd]
   #16 /lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7f8fa7adc22b]
   #17 /lib64/libtevent.so.0(+0x8ba7) [0x7f8fa7adfba7]
   #18 /usr/lib64/samba/libsmbd-base-samba4.so(smbd_process+0x5e1)
[0x7f8faade6851]
   #19 /usr/sbin/smbd(+0xcdd0) [0x558d16af5dd0]
   #20 /lib64/libtevent.so.0(+0xa83b) [0x7f8fa7ae183b]
   #21 /lib64/libtevent.so.0(+0x8c07) [0x7f8fa7adfc07]
   #22 /lib64/libtevent.so.0(_tevent_loop_once+0x9d) [0x7f8fa7adbffd]
   #23 /lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7f8fa7adc22b]
   #24 /lib64/libtevent.so.0(+0x8ba7) [0x7f8fa7adfba7]
   #25 /usr/sbin/smbd(main+0x16d7) [0x558d16af0d37]
   #26 /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f8fa772c445]
   #27 /usr/sbin/smbd(+0x83f0) [0x558d16af13f0]
[2019/01/10 17:04:09.313331,  0] ../source3/lib/dumpcore.c:315(dump_core)

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