Bug 11279 - Panic dom_sid_compare
Summary: Panic dom_sid_compare
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services (show other bugs)
Version: 4.1.16
Hardware: x86 Other
: P5 critical (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-18 14:19 UTC by tonycpsu
Modified: 2015-05-18 14:19 UTC (History)
0 users

See Also:

Attachments
core dump (2.15 MB, application/x-core)
2015-05-18 14:19 UTC, tonycpsu 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description tonycpsu 2015-05-18 14:19:50 UTC 
Created attachment 11065 [details]
core dump

Using Samba 4.1.16 on a Synology NAS, I'm getting the following backtrace during normal usage:

../lib/util/fault.c:72: [2015/05/18 10:09:58.229099, all 0, pid=18633] fault_report
  ===============================================================
../lib/util/fault.c:73: [2015/05/18 10:09:58.229316, all 0, pid=18633] fault_report
  INTERNAL ERROR: Signal 11 in pid 18633 (4.1.16)
  Please read the Trouble-Shooting section of the Samba HOWTO
../lib/util/fault.c:75: [2015/05/18 10:09:58.229467, all 0, pid=18633] fault_report
  ===============================================================
../source3/lib/util.c:788: [2015/05/18 10:09:58.229608, all 0, pid=18633] smb_panic_s3
  PANIC (pid 18633): internal error
../source3/lib/util.c:899: [2015/05/18 10:09:58.231106, all 0, pid=18633] log_stack_trace
  BACKTRACE: 25 stack frames:
   #0 /lib/libsmbconf.so.0(log_stack_trace+0x29) [0xf6575b09]
   #1 /lib/libsmbconf.so.0(smb_panic_s3+0x31) [0xf6575c11]
   #2 /lib/libsamba-util.so.0(smb_panic+0x3a) [0xf6a973ca]
   #3 /lib/libsamba-util.so.0(+0x17651) [0xf6a97651]
   #4 [0xf7726400]
   #5 /usr/lib/samba/libsamba-security.so(dom_sid_compare+0x29) [0xf5e96019]
   #6 /usr/lib/samba/libsamba-security.so(dom_sid_equal+0x23) [0xf5e960b3]
   #7 /usr/lib/samba/libsamba-security.so(security_token_is_sid+0x2c) [0xf5e9a55c]
   #8 /usr/lib/samba/libsamba-security.so(security_token_is_system+0x25) [0xf5e9a605]
   #9 /usr/lib/samba/libsamba-security.so(security_session_user_level+0x32) [0xf5e9c4f2]
   #10 /usr/lib/samba/libsmbd_base.so(reply_sesssetup_and_X+0x12b4) [0xf68676c4]
   #11 /usr/lib/samba/libsmbd_base.so(+0x11420d) [0xf68a520d]
   #12 /usr/lib/samba/libsmbd_base.so(+0x11553f) [0xf68a653f]
   #13 /usr/lib/samba/libsmbd_base.so(+0x115a5b) [0xf68a6a5b]
   #14 /lib/libsmbconf.so.0(run_events_poll+0x2b5) [0xf658d595]
   #15 /lib/libsmbconf.so.0(+0x34712) [0xf658d712]
   #16 /lib/libtevent.so.0(_tevent_loop_once+0xb8) [0xf6779fd8]
   #17 /usr/lib/samba/libsmbd_base.so(smbd_process+0xecc) [0xf68a833c]
   #18 /usr/bin/smbd(+0x9c79) [0xf7750c79]
   #19 /lib/libsmbconf.so.0(run_events_poll+0x2b5) [0xf658d595]
   #20 /lib/libsmbconf.so.0(+0x34712) [0xf658d712]
   #21 /lib/libtevent.so.0(_tevent_loop_once+0xb8) [0xf6779fd8]
   #22 /usr/bin/smbd(main+0x1666) [0xf774cbe6]
   #23 /lib/libc.so.6(__libc_start_main+0xf3) [0xf600b0c3]
   #24 /usr/bin/smbd(+0x63a1) [0xf774d3a1]
../source3/lib/dumpcore.c:317: [2015/05/18 10:09:58.232641, all 0, pid=18633] dump_core
  dumping core in /volume1


Other than upgrading the Synology OS to the latest 5.2-5565 release, I don't think there have been any other changes to samba config or anything that should impact normal samba operations.

I did see there's an old bug involving dom_sid_compare (#8567) that was fixed in v3.6.something, but couldn't find any other reports of this issue in 4.1.x.

Core dump is attached.