Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp1822039ybb; Thu, 26 Mar 2020 07:58:55 -0700 (PDT) X-Google-Smtp-Source: ADFU+vv2tQRG7zsdcm/fxjQ2xPaYf34b1qbBvt+750ZlAs6J3c7Wpjf6JcWJEHXEvLiC/l7mvHGU X-Received: by 2002:a05:6830:1313:: with SMTP id p19mr6785409otq.179.1585234735375; Thu, 26 Mar 2020 07:58:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585234735; cv=none; d=google.com; s=arc-20160816; b=et3WyJHH5jpTVfNo9rqVaJb0xypWUVxwZewQpgcpu7SR+vpN3j9jSmnukyy4XH0axZ ZJclphqE8ib+f1gnMsRCfHbdX+p2a4TAOY7WFQrCf+nwHpdH1r9ksdThIJNteqU+ismg mXHoEOYqRDO6S0MqFvnxYuBqDnTeQhmeenQCe0FTsT7DOsLWBBvwDBO4Z7wcEHZsxQsw YEznDOOrBC2gaUnRE7eSa68Ifp88BX0HnRHcWzb2ZSk/AAEBHvrpZlvKm6lOI7+EozXp stEpHklQ3rtp6Z1V8Ze6E/T0nukv16dsV+xjB79iCcoqGprvklhvGao1hIfWII9VnKrB c+3A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=/W8+00l9EB/c0JohvrKdE6x/Q5VZa1OSakA3zjUQXVY=; b=Aw8NnXzkl2UTGrpz7pVZ+D9T0F+2JR1UeqmzzJ4vAfwlguKjiOg04gBaAtx94APY2C 45hArxNZocrdiYSS3e+2Y6de4euLvqiTPVNMS33lO8DtqgXBoHdj07QmV2WemdyKuK5K n2NcfEKVIXyZGlF0kYV6pVwCSOcvOZA0JtGeRUAgBw7cEWw7W/pc956v2SqAKrdwXqdV Wu3KAVGBiTBkKZQu24/08LHqa+XbqTf1YTxg+Rb0PjI3U0krn1VLQs0HNRp823px1TK9 7qH98SUlGGzrEoNQ6FSPj6/KoEOQUhhULhRV0eQAwmhWhHZpSRSvNujqM5LIonQ2CSAc 7daw== 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 e14si1312597otf.226.2020.03.26.07.58.42; Thu, 26 Mar 2020 07:58:55 -0700 (PDT) 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 S1726270AbgCZO6B (ORCPT + 99 others); Thu, 26 Mar 2020 10:58:01 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:60130 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726318AbgCZO6B (ORCPT ); Thu, 26 Mar 2020 10:58:01 -0400 Received: from callcc.thunk.org (pool-72-93-95-157.bstnma.fios.verizon.net [72.93.95.157]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 02QEvvIt002679 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 26 Mar 2020 10:57:58 -0400 Received: by callcc.thunk.org (Postfix, from userid 15806) id 62F7B420EBA; Thu, 26 Mar 2020 10:57:57 -0400 (EDT) Date: Thu, 26 Mar 2020 10:57:57 -0400 From: "Theodore Y. Ts'o" To: Eric Whitney Cc: linux-ext4@vger.kernel.org Subject: Re: [PATCH] ext4: disable dioread_nolock whenever delayed allocation is disabled Message-ID: <20200326145757.GT53396@mit.edu> References: <20200319150028.24592-1-enwlinux@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200319150028.24592-1-enwlinux@gmail.com> Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Thu, Mar 19, 2020 at 11:00:28AM -0400, Eric Whitney wrote: > The patch "ext4: make dioread_nolock the default" (244adf6426ee) causes > generic/422 to fail when run in kvm-xfstests' ext3conv test case. This > applies both the dioread_nolock and nodelalloc mount options, a > combination not previously tested by kvm-xfstests. The failure occurs > because the dioread_nolock code path splits a previously fallocated > multiblock extent into a series of single block extents when overwriting > a portion of that extent. That causes allocation of an extent tree leaf > node and a reshuffling of extents. Once writeback is completed, the > individual extents are recombined into a single extent, the extent is > moved again, and the leaf node is deleted. The difference in block > utilization before and after writeback due to the leaf node triggers the > failure. > > The original reason for this behavior was to avoid ENOSPC when handling > I/O completions during writeback in the dioread_nolock code paths when > delayed allocation is disabled. It may no longer be necessary, because > code was added in the past to reserve extra space to solve this problem > when delayed allocation is enabled, and this code may also apply when > delayed allocation is disabled. Until this can be verified, don't use > the dioread_nolock code paths if delayed allocation is disabled. > > Signed-off-by: Eric Whitney Applied, thanks. - Ted