[Pkg-samba-maint] DO NOT REPLY [Bug 6651] smbd SIGSEGV when breaking oplocks

[samba-bugs at samba.org]

https://bugzilla.samba.org/show_bug.cgi?id=6651





------- Comment #16 from petr at vandrovec.name  2009-08-24 21:32 CST -------
I'm afraid that there is still some problem...  Unfortunately I have no idea
where that thing dumped core file - definitely not into
/usr/local/samba/var/cores/smbd, that one is empty...

[2009/08/23 01:18:08,  1] smbd/service.c:1050(make_connection_snum)
  petr-win2 (::ffff:10.20.86.92) connect to service rootfs initially as user
petr (uid=884, gid=201) (pid 14668)
[2009/08/24 19:22:07,  0] lib/fault.c:41(fault_report)
  ===============================================================
[2009/08/24 19:22:07,  0] lib/fault.c:42(fault_report)
  INTERNAL ERROR: Signal 11 in pid 14668 (3.4.0-GIT-f9c0f88-devel)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2009/08/24 19:22:07,  0] lib/fault.c:44(fault_report)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2009/08/24 19:22:07,  0] lib/fault.c:45(fault_report)
  ===============================================================
[2009/08/24 19:22:07,  0] lib/util.c:1447(smb_panic)
  PANIC (pid 14668): internal error
[2009/08/24 19:22:07,  0] lib/util.c:1551(log_stack_trace)
  BACKTRACE: 17 stack frames:
   #0 /usr/local/samba/sbin/smbd(log_stack_trace+0x1c) [0x7fc8dc27ec3f]
   #1 /usr/local/samba/sbin/smbd(smb_panic+0x55) [0x7fc8dc27ed41]
   #2 /usr/local/samba/sbin/smbd [0x7fc8dc26fa19]
   #3 /lib/libpthread.so.0 [0x7fc8da6be720]
   #4 /usr/local/samba/sbin/smbd(push_file_id_24+0) [0x7fc8dc2a29d4]
   #5 /usr/local/samba/sbin/smbd(break_kernel_oplock+0x25) [0x7fc8dc2baa88]
   #6 /usr/local/samba/sbin/smbd [0x7fc8dc2bb12c]
   #7 /usr/local/samba/sbin/smbd(tevent_common_check_signal+0xf7)
[0x7fc8dc28ecb1]
   #8 /usr/local/samba/sbin/smbd(run_events+0x30) [0x7fc8dc28d2ff]
   #9 /usr/local/samba/sbin/smbd(smbd_process+0x82f) [0x7fc8dc0a2f00]
   #10 /usr/local/samba/sbin/smbd [0x7fc8dc58b0aa]
   #11 /usr/local/samba/sbin/smbd(run_events+0x130) [0x7fc8dc28d3ff]
   #12 /usr/local/samba/sbin/smbd [0x7fc8dc28d670]
   #13 /usr/local/samba/sbin/smbd(_tevent_loop_once+0x87) [0x7fc8dc28d9e7]
   #14 /usr/local/samba/sbin/smbd(main+0xf85) [0x7fc8dc58c1ed]
   #15 /lib/libc.so.6(__libc_start_main+0xe6) [0x7fc8d8e6b5c6]
   #16 /usr/local/samba/sbin/smbd [0x7fc8dc02e7d9]
[2009/08/24 19:22:07,  0] lib/util.c:1452(smb_panic)
  smb_panic(): calling panic action [/usr/share/samba/panic-action 14668]
[2009/08/24 19:22:08,  0] lib/util.c:1460(smb_panic)
  smb_panic(): action returned status 0
[2009/08/24 19:22:08,  0] lib/fault.c:321(dump_core)
  dumping core in /usr/local/samba/var/cores/smbd
[2009/08/24 19:22:08,  1] smbd/service.c:1050(make_connection_snum)
  petr-win2 (::ffff:10.20.86.92) connect to service petr initially as user petr
(uid=884, gid=201) (pid 2220)

I suspect that it died because "counter.seen % SA_INFO_QUEUE_COUNT" after I
managed to break 2^32 leases or something like that - in my patch I changed
SA_INFO_QUEUE_COUNT to 64 to make sure it is power of two, but in yours it
stayed at 100...  Though I have no idea whether my build could break 2^32
leases during past three days, it looks like quite a lot, so maybe some other
explanation is necessary.  Unfortunately without core I have no hints
available.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.