master smbd crash in linux oplock code
Stefan (metze) Metzmacher
metze at samba.org
Fri Feb 10 11:56:10 MST 2012
Hi Ambi,
thanks! I've pushed a fix to autobuild.
metze
> I am suspecting that your commit 641a2de (s3:smbd/oplock: pass
> smbd_server_connection to linux_init_kernel_oplocks()) introduced a
> crash bug into master when kernel oplocks are turned on:
>
> [2012/02/10 18:28:13.326196, 0, pid=465247, effective(4711, 4711),
> real(0, 0)] lib/popt_common.c:67(popt_s3_talloc_log_fn)
> smbd/oplock_linux.c:103: Type mismatch: name[struct tevent_signal]
> expected[struct smbd_server_connection]
> [2012/02/10 18:28:13.326235, 0, pid=465247, effective(4711, 4711),
> real(0, 0)] lib/util.c:807(smb_panic_s3)
> PANIC (pid 465247): smbd/oplock_linux.c:103: Type mismatch:
> name[struct tevent_signal] expected[struct smbd_server_connection]
> [2012/02/10 18:28:13.374465, 0, pid=465247, effective(4711, 4711),
> real(0, 0)] lib/util.c:918(log_stack_trace)
> BACKTRACE: 17 stack frames:
> #0 sbin/smbd(log_stack_trace+0x1f) [0x7f6d520ed8ae]
> #1 sbin/smbd(smb_panic_s3+0x6d) [0x7f6d520ed72c]
> #2 sbin/smbd(smb_panic+0x28) [0x7f6d520dc728]
> #3 /usr/lib64/libtalloc.so.2(_talloc_get_type_abort+0x7b)
> [0x7f6d5002ebbb]
> #4 sbin/smbd(+0x600541) [0x7f6d5215a541]
> #5 sbin/smbd(tevent_common_check_signal+0x194) [0x7f6d521076be]
>
>
> Cheers,
> Christian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20120210/31a49931/attachment.pgp>
More information about the samba-technical
mailing list