From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55364) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bICP2-0007zt-J2 for qemu-devel@nongnu.org; Wed, 29 Jun 2016 06:07:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bICOy-0003cu-Cx for qemu-devel@nongnu.org; Wed, 29 Jun 2016 06:07:27 -0400 References: <1466780802-30424-1-git-send-email-den@openvz.org> <1466780802-30424-3-git-send-email-den@openvz.org> <9cafd60f-ac23-863d-0225-636499904398@redhat.com> From: Evgeny Yakovlev Message-ID: <57738838.5050708@virtuozzo.com> Date: Wed, 29 Jun 2016 11:35:04 +0300 MIME-Version: 1.0 In-Reply-To: <9cafd60f-ac23-863d-0225-636499904398@redhat.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 2/3] ide: ignore retry_unit check for non-retry operations List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , "Denis V. Lunev" , qemu-block@nongnu.org, qemu-devel@nongnu.org Cc: Kevin Wolf , Fam Zheng , Max Reitz , Stefan Hajnoczi , John Snow On 28.06.2016 23:56, Paolo Bonzini wrote: > > On 24/06/2016 17:06, Denis V. Lunev wrote: >> When doing DMA request ide/core.c will set s->retry_unit to s->unit in >> ide_start_dma. When dma completes ide_set_inactive sets retry_unit to -1. >> After that ide_flush_cache runs and fails thanks to blkdebug. >> ide_flush_cb calls ide_handle_rw_error which asserts that s->retry_unit >> == s->unit. But s->retry_unit is still -1 after previous DMA completion >> and flush does not use anything related to retry. > Wouldn't the assertion fail for a PIO read/write too? Perhaps > retry_unit should be set to s->unit in ide_transfer_start too. If PIO follows DMA and fails then yes, it looks like it will trigger an assert. I am not sure about setting retry_unit in ide_transfer_start. It looks like currently only DMA I/O entries touch retry_unit at all. Does that mean that PIO, flush, etc do not support retries by design and we need to add more exceptions to assert check or is it a real bug in how retries are initialized? > > Paolo