From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0D8463A6F14 for ; Wed, 4 Mar 2026 14:34:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772634861; cv=none; b=tacL3ecgffIlJezfS1c3KhF9CABaB+joZOBJJ+xKon09Fw6Acb2cyz15pTkj+pGatDPP4JIGwUj0WNUOc3aifdoxP7W5nrAIDktjhUwDmndMayjTXqybJMbBCKhOPUH86t56ouXVlehVS5JpbjMse5U1PKZjNVhG+nwVIQiouis= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772634861; c=relaxed/simple; bh=bpuGRVu4Y18L5xc3H1PJ2lREyhify4Ay9P9h5KY76nk=; h=From:In-Reply-To:References:To:Cc:Subject:MIME-Version: Content-Type:Date:Message-ID; b=oYo3gRSZdjAw5Ma2J/UV/o6NmEEaC1WlQ1Wm8lbkCX+pCb5WDv246OdlEZ6n+X5XH0NEAfd73rAQxhty1/WFSieZgvmbEYzX3bJGc5h0tql+Zrxl6MgIAmNoph2te7xh4CdFeB/FK89dqilVZOMv9Vc8VbVxPIPkuXmA8kQx9Zc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=S35+Gxqf; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="S35+Gxqf" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1772634859; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ZLC9JL4iyVNeLfPEDV0W2Yxh7iNZYOFRw/HOSKzzhuk=; b=S35+GxqfnDyMeuj3hAGhe/v89Ard3q3ZkaUBfLnl5d3eHRXTzGrIzgC0nTD4C2knuWjyMW HMHn4CCC+6/JuXD0Qr/V3qnRXqEiKmTQcF+T40JmaF8FTg2CrgICvZki1gkDzaIQj29pbQ wpEW/CAhfrh7sjzaVJXMP9shvyhMEQY= Received: from mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-629-S9NpySwlNAOll3R8_b-uzg-1; Wed, 04 Mar 2026 09:34:14 -0500 X-MC-Unique: S9NpySwlNAOll3R8_b-uzg-1 X-Mimecast-MFC-AGG-ID: S9NpySwlNAOll3R8_b-uzg_1772634851 Received: from mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 8E89519560B0; Wed, 4 Mar 2026 14:34:11 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.44.32.194]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 40E33300019F; Wed, 4 Mar 2026 14:34:06 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: References: <20260304140328.112636-1-dhowells@redhat.com> <20260304140328.112636-3-dhowells@redhat.com> <114166.1772634114@warthog.procyon.org.uk> To: Christoph Hellwig Cc: dhowells@redhat.com, Matthew Wilcox , Jens Axboe , Leon Romanovsky , Christian Brauner , Paulo Alcantara , netfs@lists.linux.dev, linux-afs@lists.infradead.org, linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org, ceph-devel@vger.kernel.org, v9fs@lists.linux.dev, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Paulo Alcantara , Steve French , Namjae Jeon , Tom Talpey , Chuck Lever Subject: Re: [RFC PATCH 02/17] vfs: Implement a FIEMAP callback Precedence: bulk X-Mailing-List: linux-cifs@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <156718.1772634844.1@warthog.procyon.org.uk> Date: Wed, 04 Mar 2026 14:34:04 +0000 Message-ID: <156719.1772634844@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.4 Christoph Hellwig wrote: > > So I have to stick with SEEK_DATA/SEEK_HOLE for this? > > Yes. Why do you even want to move away from that? It's the far > better API. Of course like all other reporting APIs it still is > racy, but has far less problems than fiemap. To find the next two extents of data, say, I have to make four calls into the backing filesystem rather than one - with all the context set up and locking those might incur. Granted, the vast majority of files aren't sparse, so one pair of SEEK_DATA/SEEK_HOLE should be able to establish that. David