Package: samba
Version: 2:4.2.10+dfsg-0+deb8u2
Severity: important
Tags: patch,upstream,fixed-upstream

Dear maintainers,

after upgrading out clustered samba to samba 4.2.10 (thanks for that btw,
it solved quite a few headaches of mine!) we started to exprience weird
panics in samba that looked like this:
  BACKTRACE: 25 stack frames:
   #0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1a) 
[0x7f8fead79f5a]
   #1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) 
[0x7f8fead7a040]
   #2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) 
[0x7f8feca33e5f]
   #3 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(update_num_read_oplocks+0x101)
 [0x7f8fec638881]
   #4 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x1082dd) 
[0x7f8fec5e52dd]
   #5 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x10a2b1) 
[0x7f8fec5e72b1]
   #6 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(create_file_default+0x19c) 
[0x7f8fec5e86ac]
   #7 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x1de8d9) 
[0x7f8fec6bb8d9]
   #8 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(smb_vfs_call_create_file+0x77)
 [0x7f8fec5eef87]
   #9 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(smbd_smb2_request_process_create+0xdd8)
 [0x7f8fec61bdf8]
   #10 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(smbd_smb2_request_dispatch+0x9be)
 [0x7f8fec614fce]
   #11 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x138be8) 
[0x7f8fec615be8]
   #12 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x171) 
[0x7f8fead99a01]
   #13 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x49c77) [0x7f8fead99c77]
   #14 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) 
[0x7f8fe979c12d]
   #15 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) 
[0x7f8fe979c2cb]
   #16 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(smbd_process+0x718) 
[0x7f8fec6044a8]
   #17 /usr/sbin/smbd(+0xadd0) [0x7f8fed090dd0]
   #18 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(run_events_poll+0x171) 
[0x7f8fead99a01]
   #19 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(+0x49c77) [0x7f8fead99c77]
   #20 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) 
[0x7f8fe979c12d]
   #21 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_wait+0x1b) 
[0x7f8fe979c2cb]
   #22 /usr/sbin/smbd(main+0x17e5) [0x7f8fed08d5e5]
   #23 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f8fe940eb45]
   #24 /usr/sbin/smbd(+0x76e4) [0x7f8fed08d6e4]

There also is an upstream bug[1] dealing with a slightly different issue
that contains a fix[2] for this bug. After recompiling the debian version
of samba with this patch applied, the issue has gone.
Would be great to get that fix into Jessie: it is kind of a regression
caused by the major update of ctdb and the tdb libs.

-- Adi

[1] https://bugzilla.samba.org/show_bug.cgi?id=11844
[2] https://attachments.samba.org/attachment.cgi?id=12042

Attachment: signature.asc
Description: Digital signature

Reply via email to