diff options
Diffstat (limited to 'results/classifier/118/none/988128')
| -rw-r--r-- | results/classifier/118/none/988128 | 69 |
1 files changed, 69 insertions, 0 deletions
diff --git a/results/classifier/118/none/988128 b/results/classifier/118/none/988128 new file mode 100644 index 000000000..aa246655c --- /dev/null +++ b/results/classifier/118/none/988128 @@ -0,0 +1,69 @@ +mistranslation: 0.752 +graphic: 0.719 +device: 0.695 +semantic: 0.692 +socket: 0.689 +performance: 0.681 +x86: 0.670 +architecture: 0.654 +ppc: 0.599 +user-level: 0.591 +network: 0.580 +kernel: 0.558 +peripherals: 0.548 +KVM: 0.529 +permissions: 0.527 +vnc: 0.509 +PID: 0.465 +debug: 0.462 +assembly: 0.461 +VMM: 0.448 +register: 0.412 +virtual: 0.378 +files: 0.367 +TCG: 0.337 +risc-v: 0.308 +hypervisor: 0.286 +i386: 0.271 +arm: 0.252 +boot: 0.242 + +smbd crashes when called with "smb ports = 0" + +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? + +It communicates via standard input (just like inetd). Obviously newer versions do not need this anymore, and smbd will detect in which mode it is supposed to run. + +That switch was once introduce in 157777ef3e to add "Samba 3 support". Maybe you can check with the samba guys if that switch was actually ever required or since when it became redundant. + +Sent a patch to qemu-devel, http://article.gmane.org/gmane.comp.emulators.qemu/148378 + +The link from comment #2 does not work anymore ... does anybody know whether the fix has been included in the QEMU repository? + +[Expired for QEMU because there has been no activity for 60 days.] + |