[SCM] Hurd branch, master, updated. v0.5-17-g6a33dc6

[Richard Braun]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Hurd".

The branch, master has been updated
       via  6a33dc6cb1546acf3c5db982e3f44b41bff67b05 (commit)
       via  2e5f5e3c6d3716aec736474a198de5f7746a5450 (commit)
       via  5ab5d98fa515cd19a64e8d5868fcbae85eec9dc5 (commit)
       via  4660ac02b9723380b4581b4c6a46e54861b95059 (commit)
      from  1cfdceba98c380ad1cebb3a6b3d1f141d852c691 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 6a33dc6cb1546acf3c5db982e3f44b41bff67b05
Author: Richard Braun <address@hidden>
Date:   Fri Oct 18 01:16:08 2013 +0200

    pflocal: fix message flags on receive
    
    * pflocal/socket.c (S_socket_recv): Set the memory pointed by out_flags
    to 0 instead of the pointer.

commit 2e5f5e3c6d3716aec736474a198de5f7746a5450
Author: Richard Braun <address@hidden>
Date:   Fri Oct 18 01:16:08 2013 +0200

    pflocal: fix port leak when receiving port rights
    
    The socket_send and socket_recv routines can be used to transmit port
    rights along data. Unfortunately, pflocal retains a copy of these rights
    in the socket_recv RPC. These lingering references would in turn lead to
    other leaks in servers waiting for a no-sender notification to clean
    their resources. Since these copied rights aren't used at all by the
    server, it is safe to simply move them to the recipient instead.
    
    * pflocal/socket.c (S_socket_recv): Transmit port rights using
    MACH_MSG_TYPE_MOVE_SEND transfer type instead of MACH_MSG_TYPE_COPY_SEND.

commit 5ab5d98fa515cd19a64e8d5868fcbae85eec9dc5
Author: Richard Braun <address@hidden>
Date:   Fri Oct 18 01:16:08 2013 +0200

    libdiskfs: fix removal of socket nodes
    
    When the file system supports ifsock shortcuts, a socket node can obtain
    a right on a socket address. This reference is only lost if the address
    is destroyed, through a dead-name notification. On the other hand,
    pflocal keeps the address around until all references are dropped. This
    leads to a situation where socket nodes, addresses, and their associated
    sockets are leaked. To remedy the situation, make addresses get a light
    reference on socket nodes, and properly deallocate it when the node is
    destroyed, which will in turn make pflocal correctly remove the matching
    address and socket.
    
    * libdiskfs/ifsock.c (diskfs_S_ifsock_getsockaddr): Add a light reference
    instead of a hard one.
    * libdiskfs/node-nput.c (diskfs_nput): Deallocate right to socket address
    when cleaning light references.

commit 4660ac02b9723380b4581b4c6a46e54861b95059
Author: Richard Braun <address@hidden>
Date:   Fri Oct 18 01:16:07 2013 +0200

    pflocal: fix destruction of explicitely bound sockets
    
    Sockets must have a weak reference on the address they're bound to so
    that addr_unbind is properly called before addr_clean. For sockets that
    are automatically bound, this weak reference is created in ensure_addr.
    Do the same in sock_bind.
    
    * pflocal/sock.c (sock_bind): Handle weak reference on addr.

-----------------------------------------------------------------------

Summary of changes:
 libdiskfs/ifsock.c    |    2 +-
 libdiskfs/node-nput.c |    6 ++++++
 pflocal/sock.c        |    6 +++++-
 pflocal/socket.c      |    5 ++---
 4 files changed, 14 insertions(+), 5 deletions(-)


hooks/post-receive
-- 
Hurd