From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52048) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XPsJD-0006g6-Jd for qemu-devel@nongnu.org; Fri, 05 Sep 2014 08:08:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XPsJ6-0001DP-46 for qemu-devel@nongnu.org; Fri, 05 Sep 2014 08:08:07 -0400 Received: from mail-we0-f173.google.com ([74.125.82.173]:62874) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XPsJ5-0001DJ-Uu for qemu-devel@nongnu.org; Fri, 05 Sep 2014 08:08:00 -0400 Received: by mail-we0-f173.google.com with SMTP id t60so11682175wes.32 for ; Fri, 05 Sep 2014 05:07:59 -0700 (PDT) Message-ID: <5409A79A.8050302@6wind.com> Date: Fri, 05 Sep 2014 14:07:54 +0200 From: David Marchand MIME-Version: 1.0 References: <1409835061-19989-1-git-send-email-david.marchand@6wind.com> <1409835061-19989-2-git-send-email-david.marchand@6wind.com> <20140904155657.GD21203@redhat.com> In-Reply-To: <20140904155657.GD21203@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v5 1/3] contrib: add ivshmem client and server List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Olivier Matz , kvm , Stefan Hajnoczi , Claudio Fontana , Markus Armbruster , "qemu-devel@nongnu.org Developers" , "Gonglei (Arei)" , Martin Kletzander , Paolo Bonzini , Jani Kokkonen , Cam Macdonell Hello Michael, On 09/04/2014 05:56 PM, Michael S. Tsirkin wrote: >> + /* create the unix listening socket */ >> + sock_fd = socket(AF_UNIX, SOCK_STREAM, 0); >> + if (sock_fd < 0) { >> + debug_log(server, "cannot create socket: %s\n", strerror(errno)); >> + goto err_close_shm; >> + } >> + >> + sun.sun_family = AF_UNIX; >> + snprintf(sun.sun_path, sizeof(sun.sun_path), "%s", server->unix_sock_path); >> + unlink(sun.sun_path); > > why unlink it? Yes, this is wrong, because this means that when starting multiple servers on the same socket, the last server is the one who wins ... while I think it should be the opposite (first server wins, as it may have some connected clients). I have been scratching my head about this: when should I unlink ? My current fix unlinks from ivshmem_server_close() (which should be the right place). I need to call this when exiting, but I can only do this when the server exits gracefully (when an error occurs on the server socket or when receiving a SIGTERM). If something unexpected happens (like a bug/crash or a SIGKILL), the socket won't be unlinked and the next server process will refuse to start. Is this something acceptable ? Do you have a better idea ? Thanks. -- David Marchand