From: Theodore Ts'o Subject: Re: [PATCH v2 3/4] ext4: Add iomap support for inline data Date: Mon, 2 Oct 2017 11:02:08 -0400 Message-ID: <20171002150208.bcuv2wqqs3cpyyvz@thunk.org> References: <20170914095047.23935-1-agruenba@redhat.com> <20170914095047.23935-4-agruenba@redhat.com> <20170928175748.23b7wkjiqavpunvj@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel , linux-ext4 , linux-xfs@vger.kernel.org, Jan Kara , Christoph Hellwig To: Andreas Gruenbacher Return-path: Received: from imap.thunk.org ([74.207.234.97]:53230 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751250AbdJBPCN (ORCPT ); Mon, 2 Oct 2017 11:02:13 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-ext4-owner@vger.kernel.org List-ID: On Mon, Oct 02, 2017 at 04:39:59PM +0200, Andreas Gruenbacher wrote: > > If we race with the inline data flag getting cleared, > > ext4_iomap_begin() will return with -EAGAIN. > > Actually, in that case, ext4_iomap_begin will treat the file as non-inline. > It will not return -EAGAIN. Ah, thanks, I missed that. - Ted