[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/988128
Title:
smbd crashes when called with "smb ports = 0"
Status in QEMU:
Expired
Bug description:
The smb.conf generated by qemu-kvm contains a "smb ports = 0" directive. This
causes at least version 3.6.4 of Samba to crash with
[0] vostro:/tmp/qemu-smb.6836-0# smbd -i -s smb.conf
Unable to setup corepath for smbd: Operation not permitted
smbd version 3.6.4 started.
Copyright Andrew Tridgell and the Samba Team 1992-2011
open_sockets_smbd: No sockets available to bind to.
===============================================================
Abnormal server exit: open_sockets_smbd() failed
===============================================================
BACKTRACE: 6 stack frames:
#0 smbd(log_stack_trace+0x1a) [0x7fe50c14f8ba]
#1 smbd(+0x6a0743) [0x7fe50c3bd743]
#2 smbd(+0x6a0a41) [0x7fe50c3bda41]
#3 smbd(main+0xa52) [0x7fe50be26d42]
#4 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fe508ac0ead]
#5 smbd(+0x10a6b9) [0x7fe50be276b9]
Changing "smb ports" to a non-privilileged port works around the
issue.
I'd like to help fix this, but I am not sure what qemu-kvm's intention is
here.
Zero is not a valid port, and the smb.conf manpage does not describe any
special meaning of zero here. I found that previous versions of samba
apparently
did not bind to any port if zero was specified - but in that case, how is
qemu communicating with samba?
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/988128/+subscriptions
