From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38116) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X0899-00053h-1e for qemu-devel@nongnu.org; Thu, 26 Jun 2014 07:47:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X0892-000284-UM for qemu-devel@nongnu.org; Thu, 26 Jun 2014 07:47:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]:33685) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X0892-00027y-Hv for qemu-devel@nongnu.org; Thu, 26 Jun 2014 07:47:12 -0400 Message-ID: <53AC0839.3050302@redhat.com> Date: Thu, 26 Jun 2014 13:47:05 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1403783111-28592-1-git-send-email-batuzovk@ispras.ru> In-Reply-To: <1403783111-28592-1-git-send-email-batuzovk@ispras.ru> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] qemu-char: initialize chr_write_lock List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kirill Batuzov , qemu-devel@nongnu.org Cc: Nikita Belov , Fam Zheng , Luiz Capitulino Il 26/06/2014 13:45, Kirill Batuzov ha scritto: > chr_write_lock was introduced in commit 9005b2a7589540a3733b3abdcfbccfe7746cd1a1 > but was used uninitialized. It caused segmentation fault on windows hosts. A similar patch is already on the list. Thanks anyway for your contribution! Paolo