From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N0Jeo-0003fq-U6 for qemu-devel@nongnu.org; Tue, 20 Oct 2009 14:42:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N0Jee-0003Z4-Em for qemu-devel@nongnu.org; Tue, 20 Oct 2009 14:42:03 -0400 Received: from [199.232.76.173] (port=58627 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N0Jec-0003YM-Hl for qemu-devel@nongnu.org; Tue, 20 Oct 2009 14:41:54 -0400 Received: from mx1.redhat.com ([209.132.183.28]:29431) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N0Jec-0002gN-1M for qemu-devel@nongnu.org; Tue, 20 Oct 2009 14:41:54 -0400 Subject: Re: [Qemu-devel] [PATCH] qemu: work around for "posix-aio-compat" From: Mark McLoughlin In-Reply-To: <20091008203740.GA20727@redhat.com> References: <20091008203740.GA20727@redhat.com> Content-Type: text/plain Date: Tue, 20 Oct 2009 19:39:41 +0100 Message-Id: <1256063981.27918.6.camel@blaa> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: Mark McLoughlin List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: qemu-devel@nongnu.org On Thu, 2009-10-08 at 22:37 +0200, Michael S. Tsirkin wrote: > With commit ee3993069ff55fa6f1c64daf1e09963e340db8e4, > "posix-aio-compat: avoid signal race when spawning a thread" > winxp installation on a raw format file fails > during disk format, with a message "your > disk may be damaged". > > This commit moved signal mask from aio thread to creating thread. > It turns out if we keep the mask in aio thread as well, the problem > disappears. It should not be needed, but since this is harmless, let's > keep it around until someone inclined to debug pthread library internals > can check this issue. > > While we are at it, convert sigprocmask to pthread_sigmask > as per posix. FWIW, I just started hitting a boot hang with qemu.git and --enable-kvm on a Fedora 11 machine with a Fedora 11 guest. I bisected it back to malc's commit, found this thread, applied Michael's patch and confirmed that it fixes the problem for me too. Cheers, Mark.