From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Jin Subject: Re: [patch] xen-blkback: sync I/O after backend disconnected Date: Tue, 16 Aug 2011 14:56:30 +0800 Message-ID: <4E4A149E.5080608@oracle.com> References: <4E48A6A6.4040706@oracle.com> <20110815144610.GA3707@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110815144610.GA3707@infradead.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Christoph Hellwig Cc: "xen-devel@lists.xensource.com" , Konrad Rzeszutek Wilk , Jens Axboe , Greg Marsden , "linux-kernel@vger.kernel.org" , Ian Campbell , Kurt C Hackel List-Id: xen-devel@lists.xenproject.org On 08/15/11 22:46, Christoph Hellwig wrote: > On Mon, Aug 15, 2011 at 12:55:02PM +0800, Joe Jin wrote: >> When backend disconnect, sync IO requests to the disk. > > Care to explain why? When backend disconnect, I think we'd better flush all dirty data to the disk ASAP. > > Also you'll just need a sync_blockdev, fsync_bdev does far to many > things that don't make any sense when you don't have a file system > mounted on a device. > xen-blkback support physical device and loopback file, so I think here should be fsync_bdev()? Thanks, Joe