From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:45861) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T3MV1-0005MW-To for qemu-devel@nongnu.org; Mon, 20 Aug 2012 03:34:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T3MV0-00056X-S9 for qemu-devel@nongnu.org; Mon, 20 Aug 2012 03:34:11 -0400 Received: from mail.profihost.ag ([85.158.179.208]:34733) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T3MV0-00056L-In for qemu-devel@nongnu.org; Mon, 20 Aug 2012 03:34:10 -0400 Message-ID: <5031E86F.2000000@profihost.ag> Date: Mon, 20 Aug 2012 09:34:07 +0200 From: Stefan Priebe - Profihost AG MIME-Version: 1.0 References: <1345326543-10677-1-git-send-email-pbonzini@redhat.com> <50309BEE.3090602@profihost.ag> <5030E5F2.7060903@redhat.com> <50313D03.8040101@profihost.ag> <5031E5CC.7090306@redhat.com> In-Reply-To: <5031E5CC.7090306@redhat.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH RFT 0/3] iscsi: fix NULL dereferences / races between task completion and abort List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org, ronniesahlberg@gmail.com Am 20.08.2012 09:22, schrieb Paolo Bonzini: > Il 19/08/2012 21:22, Stefan Priebe - Profihost AG ha scritto: >> >>> No problem, my fault---I'm just back and I haven't really started again >>> all my stuff, so the patch was not tested. >>> >>> This should fix it, though. >> >> Booting works fine now. But the VM starts to hang after trying to unmap >> large regions. No segfault or so just not reacting anymore. > > This is expected; unfortunately cancellation right now is a synchronous > operation in the block layer. SCSI is the first big user of > cancellation, and it would indeed benefit from asynchronous cancellation. > > Without these three patches, you risk corruption in case the following > happens: > > qemu target > ----------------------------------- > send unmap --------> > cancel unmap ------> > send write --------> > <---------------- complete write > > <---------------- complete unmap > <---------------- cancellation done (unmap complete) mhm OK that makes sense. But i cannot even login via SSH and i also see no cancellation message in kernel log. So what is the right way to test these patches? With my version i can still work via SSH. Stefan