Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp609954iob; Tue, 3 May 2022 06:07:11 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz1ZtAndc6YTtuYUc9UTAVeat+JhDqYLe+qEDzyehETobjJ60BoXgdtSv23kNsPJefgNS7m X-Received: by 2002:a05:651c:a12:b0:250:5a71:5a50 with SMTP id k18-20020a05651c0a1200b002505a715a50mr5129681ljq.288.1651583231152; Tue, 03 May 2022 06:07:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651583231; cv=none; d=google.com; s=arc-20160816; b=aOw/0rWAA7AVGfEvVfVooof5N/Jomnud/K0L0ghko5M9+JPx1NY7WqQAMOr3xVFlTy Q15OP+7xQ9GTpCvkkmEMvMW2afoOqc3Hb9AmQTC7v0HWlCKDtX8QJOKmh+mA22abwBrm 65CrsbbWk7Meoxaj1L6x1+51dMVTHkoh8mrFN6TYtxhwHXJAmXTyjMORXETMWZjeoahH Er2wsL3vLUeyrlX6rdmbUK9Puc3tnGXnrzcvOpjxTOugHzaLX8f/Y2uNAMLVFzTpeOJO UHIRFdZRnQVOv5borhfl6Q7QZfc0KaO9mGz8t8ge0mGYQ2x99yLmNVaBQ0KMK50n0D6K +K7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=IbqF+ckkOVzl+G6oTpFUQT7LnpeiAwn/4wISs4deRYw=; b=bdumZZF1SMeAq9QVI6nkhQLorh/1XUkkhOQDIs12Do1NHYjJkFziBojvBrnJcJCF5D L9bLbk358rMO4OvszPImddamQ0QrUa4nkDi2X+MwzN/tYwwwT45FJJqTEWII0/yHkJU/ oClx0DHwT/IU3BmLMkGL959/33dCm2I2ldure9cPPAHYG2hI1p/7FsYAUwUlBsXb/HKi 0RCpDJohqqUfSHSWedEHkLp7zvcLcPqIt8XxP7JhboeGHvQ+B5OAlyhNaSJr0If/3x2b YNCQJBo1evSo9Czu8lJRzQzF0NsV/rf+rx2qHz2eJA4w/koiWRI10eWom1KsHesIIuvP MFbw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id h3-20020a2eb0e3000000b0024b6576315csi14771783ljl.33.2022.05.03.06.06.17; Tue, 03 May 2022 06:07:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234547AbiECMhQ (ORCPT + 99 others); Tue, 3 May 2022 08:37:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47650 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232602AbiECMhP (ORCPT ); Tue, 3 May 2022 08:37:15 -0400 Received: from gardel.0pointer.net (gardel.0pointer.net [85.214.157.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8899F1EAE4; Tue, 3 May 2022 05:33:42 -0700 (PDT) Received: from gardel-login.0pointer.net (gardel-mail [IPv6:2a01:238:43ed:c300:10c3:bcf3:3266:da74]) by gardel.0pointer.net (Postfix) with ESMTP id 5366FE804AA; Tue, 3 May 2022 14:33:40 +0200 (CEST) Received: by gardel-login.0pointer.net (Postfix, from userid 1000) id C5E07160011; Tue, 3 May 2022 14:33:39 +0200 (CEST) Date: Tue, 3 May 2022 14:33:39 +0200 From: Lennart Poettering To: "Jason A. Donenfeld" Cc: Alexander Graf , linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, Dominik Brodowski , Greg Kroah-Hartman , Theodore Ts'o , Colm MacCarthaigh , Torben Hansen , Jann Horn Subject: Re: [PATCH 2/2] random: add fork_event sysctl for polling VM forks Message-ID: References: <20220502140602.130373-1-Jason@zx2c4.com> <20220502140602.130373-2-Jason@zx2c4.com> <7a1cfd1c-9f0e-f134-e544-83ee6d3cd9c9@amazon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Di, 03.05.22 13:55, Jason A. Donenfeld (Jason@zx2c4.com) wrote: > I'm still not convinced there's value in having a counter or a UUID, but > if you had to choose, would you prefer a counter or a UUID? It sounds > like the former, because you see a use for distinguishing between zero > and non-zero? Or did you finally agree with me that vmgenid isn't > granular enough for that? I would prefer a monotonic counter, since it allows answering questions like the following: 1. Did this image get cloned at all? (i.e. counter != 0; usecase as per the MAC address discussion) 2. Did the image get cloned since the last time I looked? (i.e. counter != my_previously_saved_counter; usecase: detect clones in an "offline" fashion, i.e. from a component that doesn't continously run, but only from time to time) 3. How many clones did I miss? (i.e. missed_clones = my_previously_saved_counter - counter; usecase: catch up with generating proxy D-Bus signal messages for clones). There might be more. Using a UUID would not give us #1 or #3. It would deliver #2 however. Lennart -- Lennart Poettering, Berlin