Today I compiled the latest version of the smartos (illumos-joyent commit
d4deba385f81ee4da156448f5e42b881e84c783f), and Samba stopped working.
Simple test case inside zone with samba server running:

# smbclient -A smb.auth -L localhost
zsh: IOT instruction (core dumped)  smbclient -A smb.auth -L localhost

# mdb /var/cores/mdb smbclient.smb1.3123.1411652997.core
Loading modules: [ libumem.so.1 libc.so.1 ld.so.1 ]
> ::stack
libc.so.1`_lwp_kill+0x15(1, 6, 0, 1, fe6c2000, fe69ed73)
libc.so.1`raise+0x2b(6, fe6e0900, fe733610, fe6c2000)
libumem.so.1`umem_do_abort+0x2b(fe6c2000, 0, 80466c8, fe696797, fe69ed73,
fe69eff5)
libumem.so.1`umem_err_recoverable+0x5a(fe69ed73, fe69eff5, 864ec08,
fe69efcf, 0, 3a109ec4)
libumem.so.1`process_free+0xbf(864ec08, 1, 0, feba8000)
libumem.so.1`umem_malloc_free+0x1a(864ec08, 1, 0, feb4f8ba)
libnsl.so.1`__IPv6_cleanup+0x27(8603d00, 80467bc, 8046730, 0)
libnsl.so.1`getipnodebyname+0x36e(80467c0, 1a, 8007, 80467bc, 8046954, 0)
libsocket.so.1`get_addr+0x132(0, 8607c20, 8046930, 8046930, 0, 0)
libsocket.so.1`_getaddrinfo+0x6c5(8607c20, 0, 8046a00, 80469fc, 0, 8607c20)
libsocket.so.1`getaddrinfo+0x19(8607c20, 0, 8046a00, 80469fc, 8046b7c,
80469fc)
internal_resolve_name+0x3bb(8046b6c, 8607c20, 20, 0, 8046b78, 8046b7c)
resolve_name_list+0xe8(8046bfc, 8605f58, 8607c20, 20, 8046c0c, 8046c08)
cli_connect+0xe5(8046cac, 861bc78, 8607d60, 8046d60, 8046cb0, fefc8de6)
do_connect+0xdb(8605fc8, 8607d60, 84cc423, 8607e00, 1, 0)
cli_cm_open+0x10d(8605fc8, 0, 8607d60, 84cc423, 8607e00, 1)
main+0xd62(8047b7c, fe843668, 8047bbc, 80d74a3, 5, 8047bc8)
_start+0x83(5, 8047cd0, 8047cda, 8047cdd, 8047ce6, 8047ce9)

# mdb -uM /opt/local/bin/smbclient
> ::bp getipnodebyname
> ::run -U admin -L localhost
> ::dis -w
libnsl.so.1`getipnodebyname:    pushl  %ebp
libnsl.so.1`getipnodebyname+1:  movl   %esp,%ebp
libnsl.so.1`getipnodebyname+3:  pushl  %edi
libnsl.so.1`getipnodebyname+4:  pushl  %esi
libnsl.so.1`getipnodebyname+5:  pushl  %ebx
libnsl.so.1`getipnodebyname+6:  subl   $0x48,%esp
libnsl.so.1`getipnodebyname+9:  call   +0x0
<libnsl.so.1`getipnodebyname+0xe>
libnsl.so.1`getipnodebyname+0xe:popl   %ebx
libnsl.so.1`getipnodebyname+0xf:addl   $0x57392,%ebx
libnsl.so.1`getipnodebyname+0x15:       movl   0x10(%ebp),%esi
libnsl.so.1`getipnodebyname+0x18:       leal   0xfffebdad(%ebx),%eax

After I reverted commit:
commit a6bfa5aff4e1dfafaa1c0b7ecc362190b213630e
Author: Robert Mustacchi <[email protected]>
Date:   Thu Aug 14 21:58:20 2014 +0000

    OS-3332 getaddrinfo mistakingly IPv6 maps addresses
    Reviewed by: Joshua M. Clulow <[email protected]>

Samba is working as usual.

# smbclient -A smb.auth -L localhost
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.24]

        Sharename       Type      Comment
        ---------       ----      -------
        shared          Disk      shared
        IPC$            IPC       IPC Service (smb1)
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.24]

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------



So far as I have noticed only a samba is afflicted with this commit. Is
this Samba fault in dns resolving?



-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Reply via email to