From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 73830C4743D for ; Fri, 11 Jun 2021 08:10:23 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 0D18D61357 for ; Fri, 11 Jun 2021 08:10:23 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0D18D61357 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:42606 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lrcFC-0000mi-7Z for qemu-devel@archiver.kernel.org; Fri, 11 Jun 2021 04:10:22 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:57428) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lrcEC-00078k-U5 for qemu-devel@nongnu.org; Fri, 11 Jun 2021 04:09:20 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:28074) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lrcEA-0001pZ-8S for qemu-devel@nongnu.org; Fri, 11 Jun 2021 04:09:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1623398957; 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=NM/+S7azBIWDt6YqPQmITsv3ckxEon7oATPCkwzMc0E=; b=AfFQpccU/3nPO9mT+ftcKJTjqtChVqa//PKo2rZTZM52VUN2OW+0iLt4yYNNQbOeV0Mp4K Y6yiQQ/dEZ7TXqH/BnSgpP0AJM9GwuMmJe0o1BfBVaEU0bpvAld47pxkpUZIWz1U8U3RAv I61dajmrCypJ+Kogj8BWK4CK8NR1mpo= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-12-0ZfSDlgPNTS4AndhdMNzyg-1; Fri, 11 Jun 2021 04:09:14 -0400 X-MC-Unique: 0ZfSDlgPNTS4AndhdMNzyg-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 35C99100C660; Fri, 11 Jun 2021 08:09:13 +0000 (UTC) Received: from redhat.com (ovpn-114-101.ams2.redhat.com [10.36.114.101]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A14EA60FC2; Fri, 11 Jun 2021 08:09:10 +0000 (UTC) Date: Fri, 11 Jun 2021 10:09:09 +0200 From: Kevin Wolf To: Eric Blake Subject: Re: [PATCH] qemu-{img,nbd}: Don't report zeroed cluster as a hole Message-ID: References: <20210607202204.1805199-1-nsoffer@redhat.com> <20210607212224.tiqjvvdwosvhrvz7@redhat.com> <20210610183443.clk43ngkobzyjopy@redhat.com> <20210610204617.fuj4ivqrixpz4qfj@redhat.com> MIME-Version: 1.0 In-Reply-To: <20210610204617.fuj4ivqrixpz4qfj@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=kwolf@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Received-SPF: pass client-ip=170.10.133.124; envelope-from=kwolf@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -29 X-Spam_score: -3.0 X-Spam_bar: --- X-Spam_report: (-3.0 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.199, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Vladimir Sementsov-Ogievskiy , Nir Soffer , qemu-block , QEMU Developers , Max Reitz , Nir Soffer Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" Am 10.06.2021 um 22:46 hat Eric Blake geschrieben: > On Thu, Jun 10, 2021 at 11:09:05PM +0300, Nir Soffer wrote: > > > But: > > > > > > $ qemu-img map --output=json -f qcow2 json:'{"driver":"qcow2","backing":null, \ > > > "file":{"driver":"file","filename":"top.qcow2"}}' > > > [{ "start": 0, "length": 65536, "depth": 0, "zero": true, "data": false}, > > > { "start": 65536, "length": 65536, "depth": 0, "zero": false, "data": true, "offset": 327680}, > > > { "start": 131072, "length": 131072, "depth": 0, "zero": true, "data": false}] > > > > > > also reports the entire file at "depth":0, which is misleading, since > > > we have just been arguing from the qemu:allocation-depth perspective > > > (and also from bdrv_block_status) that the qcow2 image is NOT 100% > > > allocated (in the sense where allocation == data comes locally). > > > Perhaps it might be better if we tweaked the above qemu-img map to > > > produce: > > > > > > [{ "start": 0, "length": 65536, "depth": -1, "zero": true, "data": false}, > > > { "start": 65536, "length": 65536, "depth": 0, "zero": false, "data": true, "offset": 327680}, > > > { "start": 131072, "length": 65536, "depth": 0, "zero": true, "data": false}, > > > { "start": 196608, "length": 65536, "depth": -1, "zero": true, "data": false}] > > > > It will be more consistent with "offset" to drop "depth" from output > > if we don't have it: > > > > [{ "start": 0, "length": 65536, "zero": true, "data": false}, > > { "start": 65536, "length": 65536, "depth": 0, "zero": false, > > "data": true, "offset": 327680}, > > { "start": 131072, "length": 65536, "depth": 0, "zero": true, > > "data": false}, > > { "start": 196608, "length": 65536, "zero": true, "data": false}] > > Yes, that might work as well. But we didn't previously document > depth to be optional. Removing something from output risks breaking > more downstream tools that expect it to be non-optional, compared to > providing a new value. A negative value isn't any less unexpected than a missing key. I don't think any existing tool would be able to handle it. Encoding different meanings in a single value isn't very QAPI-like either. Usually strings that are parsed are the problem, but negative integers really isn't that much different. I don't really like this solution. Leaving out the depth feels like a better suggestion to me. But anyway, this seems to only happen at the end of the backing chain. So if the backing chain consistents of n images, why not report 'depth': n + 1? So, in the above example, you would get 1. I think this has the best chances of tools actually working correctly with the new output, even though it's still not unlikely to break something. Kevin