Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp1250351ybx; Tue, 5 Nov 2019 12:56:20 -0800 (PST) X-Google-Smtp-Source: APXvYqyMcmrdPyFhyi2Erbv1IMPsgHDh1nl0FJocPkR8M1tUtiv8F/6BzJRUTgs7YKL3p+eBpAWz X-Received: by 2002:aa7:d552:: with SMTP id u18mr38567369edr.86.1572987380590; Tue, 05 Nov 2019 12:56:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1572987380; cv=none; d=google.com; s=arc-20160816; b=nQxv/6EYIgUzEm2V43P4tt5xYWFCNxbqGam95YNCMB4LANn5Np79Nv24/sWyD0xfPA YDrMhl4MuNRMcjbqajiTJYG8b0464ADbw72eNcL+FClaS6+SAvi4YWu3YnfCH08YqhC7 DTaeLe1Aa5ICsmZnZM/PZWkYG1ahZnw7PleueoxcJ+DpnttgD3RQWaaKxqRBE7chlPKf o25IEpWdXwSVtJxjWTTfFj/4o8PzBn59OzjFyDx4Xtlmc5JSB53Zbq4ywN//4qHjkFry YSjMTIvMbJ40TDs38FEJAG/hria5bl781M+6m3kcxVk93Tcby1yhYv9NcNEO89rcSdt5 N7bA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=VOV8gaq9b2ldXyXQbVnJpvxdTTLHBHsgZx3FxWVdgYk=; b=kC0DArhClcVnImOwgGXD1teG3i8Qf/uupJ76PvEzq+vhsA3fkz+io7XTRpQ4mK3Rc1 BaIynfH6ECMmx52uaXuhWAUu63Ha35t+DyhBqtVdwkoQnFJ2z9ypq4EfVTmcyZyURqLI uRBSAZJ3U011LRKRrhLPK4vTARvNYcffijXl2N4U8nFBrmLsamLt4musDDh+Ud+Q+O+d i2G2Jj/RDS7C4tGNYN+xcI3qNG6PS8FpgQDmgvVIKZqBM/bP7aUSWmNN0OGC+8ffPLK0 CWjQPmJ8sdx54lddnemFB0t27kpSeAZdlStbze5G0JSZjjmxy8G4g3b6dn+RY70zbW5Q 1CHw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b7si11537390edb.439.2019.11.05.12.55.53; Tue, 05 Nov 2019 12:56:20 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729739AbfKEUxP (ORCPT + 99 others); Tue, 5 Nov 2019 15:53:15 -0500 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:57401 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725806AbfKEUxP (ORCPT ); Tue, 5 Nov 2019 15:53:15 -0500 Received: from callcc.thunk.org (ip-12-2-52-196.nyc.us.northamericancoax.com [196.52.2.12]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id xA5Kr6PO004643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 5 Nov 2019 15:53:07 -0500 Received: by callcc.thunk.org (Postfix, from userid 15806) id DB589420311; Tue, 5 Nov 2019 15:53:03 -0500 (EST) Date: Tue, 5 Nov 2019 15:53:03 -0500 From: "Theodore Y. Ts'o" To: Matthew Bobrowski Cc: Jan Kara , adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, riteshh@linux.ibm.com Subject: Re: [PATCH v7 11/11] ext4: introduce direct I/O write using iomap infrastructure Message-ID: <20191105205303.GA26959@mit.edu> References: <20191105135932.GN22379@quack2.suse.cz> <20191105203158.GA1739@bobrowski> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191105203158.GA1739@bobrowski> User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Wed, Nov 06, 2019 at 07:32:00AM +1100, Matthew Bobrowski wrote: > > Otherwise you would write out and invalidate too much AFAICT - the 'offset' > > is position just before we fall back to buffered IO. Otherwise this hunk > > looks good to me. > > Er, yes. That's right, it should rather be 'err' instead or else we > would write/invalidate too much. I actually had this originally, but I > must've muddled it up while rewriting this patch on my other computer. > > Thanks for picking that up! I can fix that up in my tree, unless there are any other changes that we need to make. - Ted