From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60228) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fizcA-0004E0-Vw for qemu-devel@nongnu.org; Fri, 27 Jul 2018 06:04:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fizc7-00073G-2H for qemu-devel@nongnu.org; Fri, 27 Jul 2018 06:04:50 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:54648 helo=mx1.redhat.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fizc6-00070k-SJ for qemu-devel@nongnu.org; Fri, 27 Jul 2018 06:04:46 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6662740216E5 for ; Fri, 27 Jul 2018 10:04:45 +0000 (UTC) Date: Fri, 27 Jul 2018 12:04:42 +0200 From: Kevin Wolf Message-ID: <20180727100442.GC4355@localhost.localdomain> References: <20180724084739.580-1-famz@redhat.com> <20180727092215.GG19416@lemon.usersys.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180727092215.GG19416@lemon.usersys.redhat.com> Subject: Re: [Qemu-devel] [PATCH 0/2] iotests: Fix 226 on _my_ system List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Fam Zheng Cc: qemu-devel@nongnu.org Am 27.07.2018 um 11:24 hat Fam Zheng geschrieben: > On Tue, 07/24 16:47, Fam Zheng wrote: > > Something has locked /dev/null on my system (I still don't know what to do with > > the annoying incapability of lslocks, or more precisely /proc/locks, on > > inspecting OFD lock information), and as a result 226 cannot pass due to the > > unexpected image locking error. > > > > Fix the test case by disabling locking, and add a doc text about using test > > images. > > > > Fam Zheng (2): > > docs: Describe using images in writing iotests > > iotests: Don't lock /dev/null in 226 > > > > docs/devel/testing.rst | 11 +++++++++++ > > tests/qemu-iotests/226 | 4 ++-- > > 2 files changed, 13 insertions(+), 2 deletions(-) > > Kevin, could you apply this for 3.0 too? Sure, applied to the block branch. Out of curiosity, did you find out what had locked the devices? Kevin