Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935744Ab1ETMUM (ORCPT ); Fri, 20 May 2011 08:20:12 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:35101 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935420Ab1ETMUL (ORCPT ); Fri, 20 May 2011 08:20:11 -0400 Date: Fri, 20 May 2011 08:20:10 -0400 From: Christoph Hellwig To: Alex Bligh Cc: linux-kernel@vger.kernel.org Subject: Re: REQ_FLUSH, REQ_FUA and open/close of block devices Message-ID: <20110520122010.GA25628@infradead.org> References: <10C5890F8F477E959B993BFA@nimrod.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10C5890F8F477E959B993BFA@nimrod.local> User-Agent: Mutt/1.5.21 (2010-09-15) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 418 Lines: 10 On Thu, May 19, 2011 at 04:06:27PM +0100, Alex Bligh wrote: > Should a close() of a dirty block device result in a REQ_FLUSH? No, why would it? That's what fsync is for. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/