Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp225198ybh; Fri, 13 Mar 2020 20:50:03 -0700 (PDT) X-Google-Smtp-Source: ADFU+vv3FTM/Xrz70s9LhGzGRWOaEpD2e51ur2PcOpBVNYvOPuD02e+l/DMceh/HLOJjJuKLAs/L X-Received: by 2002:aca:50d0:: with SMTP id e199mr9783887oib.133.1584157802902; Fri, 13 Mar 2020 20:50:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584157802; cv=none; d=google.com; s=arc-20160816; b=xap0ToCAoFndPb8aHlXnD61AGrdcYsyQyG1zYwNRbI2+JTXXxZNIV4CiSDLLAtJLVg fMlhnjLCrlcWHLk+n/BjgITiYdcShDy5RIS20m09vb+tk7M9OC4xLsCyKlsRZOlCZS0P Z0B838hjMRsSUz6OC5YGdk2s1MIIzvxs51RQwarZf20ItnEOKvkukXo0ghmv5xNXoO33 BeeI21Ev01CHVME8Ijh9BbasQ00JoBdmCJMiFP8rKNufbULCQSMuy3sE5NeN8fJSK2ER bnybe2vtXfhM+lVzKWu/9H8Bq0uJ6e8D3PhLVcCXifQwGfNmL05rkOEPycoIrhqFLpxI AHow== 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=Bj1X4rTCgbaAL6p44DDSRAQJVrjDwr+BoC69aSrxNrU=; b=gnXlScrl2UwEeGiF6bMepXkRw/TyI06HC7+Pmsq8DXXPRPSPxTa7cST4ud0eB6zUQ7 DqiachveJgU3+Cv1cdomBsSaPAziXX1ka1MCOvFHGV8tzRFCddqB1IeAyoBEachrfJ4G A3SUsvNlgPitlyEtMRslY/fObfpIts7tmZoy7Xna53ve/HDd80t/1YE0PUyWlTI3QwbU Ruuo2F8hizinAcZeJ8gNYLDgrW3oHwoTZyQ/m2lj/Z8wKLRqC7QC6jhYTpwNhJwpCh23 E2XIYb6C9L2CTS6eyueZ9Lk1AGVVcxiyHlKbdnyK7Zr1c2BcQfOABhTpg9XkI5bz7ioP oPdA== 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 88si6081824otv.12.2020.03.13.20.49.51; Fri, 13 Mar 2020 20:50:02 -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 S1726480AbgCNDtQ (ORCPT + 99 others); Fri, 13 Mar 2020 23:49:16 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:39963 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726399AbgCNDtQ (ORCPT ); Fri, 13 Mar 2020 23:49:16 -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 02E3mxYt004898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 13 Mar 2020 23:48:59 -0400 Received: by callcc.thunk.org (Postfix, from userid 15806) id 1F870420E5E; Fri, 13 Mar 2020 23:48:59 -0400 (EDT) Date: Fri, 13 Mar 2020 23:48:59 -0400 From: "Theodore Y. Ts'o" To: Ritesh Harjani Cc: Matthew Wilcox , linux-ext4@vger.kernel.org, jack@suse.cz, adilger.kernel@dilger.ca, linux-fsdevel@vger.kernel.org, darrick.wong@oracle.com, hch@infradead.org, cmaiolino@redhat.com, david@fromorbit.com Subject: Re: [PATCHv5 6/6] Documentation: Correct the description of FIEMAP_EXTENT_LAST Message-ID: <20200314034859.GM225435@mit.edu> References: <5a00e8d4283d6849e0b8f408c8365b31fbc1d153.1582880246.git.riteshh@linux.ibm.com> <20200228153650.GG29971@bombadil.infradead.org> <20200302081007.8B710A4070@d06av23.portsmouth.uk.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200302081007.8B710A4070@d06av23.portsmouth.uk.ibm.com> Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Mon, Mar 02, 2020 at 01:40:06PM +0530, Ritesh Harjani wrote: > > Thanks for the review. > Will make the suggested changes and send a v6. I didn't see a v6, so I revised this patch to read: commit 499800830ae5d44ae29f69c98ab9893f0425cb51 Author: Ritesh Harjani Date: Fri Feb 28 14:56:59 2020 +0530 Documentation: correct the description of FIEMAP_EXTENT_LAST Currently FIEMAP_EXTENT_LAST is not working consistently across different filesystem's fiemap implementations. So add more information about how else this flag could set in other implementation. Signed-off-by: Ritesh Harjani Link: https://lore.kernel.org/r/5a00e8d4283d6849e0b8f408c8365b31fbc1d153.1582880246.git.riteshh@linux.ibm.com Signed-off-by: Theodore Ts'o diff --git a/Documentation/filesystems/fiemap.txt b/Documentation/filesystems/fiemap.txt index f6d9c99103a4..ac87e6fda842 100644 --- a/Documentation/filesystems/fiemap.txt +++ b/Documentation/filesystems/fiemap.txt @@ -115,8 +115,10 @@ data. Note that the opposite is not true - it would be valid for FIEMAP_EXTENT_NOT_ALIGNED to appear alone. * FIEMAP_EXTENT_LAST -This is the last extent in the file. A mapping attempt past this -extent will return nothing. +This is generally the last extent in the file. A mapping attempt past +this extent may return nothing. Some implementations set this flag to +indicate this extent is the last one in the range queried by the user +(via fiemap->fm_length). * FIEMAP_EXTENT_UNKNOWN The location of this extent is currently unknown. This may indicate - Ted