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=-18.3 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL autolearn=ham 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 2AA32C47082 for ; Tue, 8 Jun 2021 14:31:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 140886100B for ; Tue, 8 Jun 2021 14:31:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233405AbhFHOdo (ORCPT ); Tue, 8 Jun 2021 10:33:44 -0400 Received: from linux.microsoft.com ([13.77.154.182]:35020 "EHLO linux.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232911AbhFHOdc (ORCPT ); Tue, 8 Jun 2021 10:33:32 -0400 Received: from mail-pj1-f44.google.com (mail-pj1-f44.google.com [209.85.216.44]) by linux.microsoft.com (Postfix) with ESMTPSA id C05AB20B83C5; Tue, 8 Jun 2021 07:31:38 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com C05AB20B83C5 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1623162698; bh=JnlE/ASrWteshDyQ1tFpfq9txCyaobzxnJrsAw9CmbY=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=tPgL4q9mybkLrEqqr7lydsUTbK69v8Hr3mCYEsNSKEbIv+fNxoMYwEIx89Eh8OeRZ BlVXzrowlasib7cfyS25H9YYWG9lrS8Cv2D0BS+sKFF82/1O9vXpt+OCtbWp0pjTDS XDNAcvd+hURQg02X9RRmCU2rer2mqvkEJDg7BxvQ= Received: by mail-pj1-f44.google.com with SMTP id k7so12022202pjf.5; Tue, 08 Jun 2021 07:31:38 -0700 (PDT) X-Gm-Message-State: AOAM533LsPzXamqa8B7rIidQMMbk8c8uN3q9U/8CL6CSxmKVrl0Qf2AD QJVznbveNLo/s86aK6wAz8/fQpiMkRRmWSUEEOs= X-Google-Smtp-Source: ABdhPJwPTRlQRIgsSDssfFRFzD1jTFn3f0nQELvDQHcXEKHqdpABjcjOa5jBr4FS/1YArSUaseYWm2IEK7XSaA+RwJk= X-Received: by 2002:a17:90b:4b49:: with SMTP id mi9mr25971333pjb.187.1623162698348; Tue, 08 Jun 2021 07:31:38 -0700 (PDT) MIME-Version: 1.0 References: <20210520135622.44625-1-mcroce@linux.microsoft.com> In-Reply-To: <20210520135622.44625-1-mcroce@linux.microsoft.com> From: Matteo Croce Date: Tue, 8 Jun 2021 16:31:02 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 0/6] block: add a sequence number to disks To: Christoph Hellwig Cc: linux-kernel@vger.kernel.org, Lennart Poettering , Luca Boccassi , Jens Axboe , Alexander Viro , Damien Le Moal , Tejun Heo , =?UTF-8?Q?Javier_Gonz=C3=A1lez?= , linux-block@vger.kernel.org, Niklas Cassel , Johannes Thumshirn , Hannes Reinecke , Matthew Wilcox , linux-fsdevel@vger.kernel.org, JeffleXu Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On Thu, May 20, 2021 at 3:56 PM Matteo Croce wrote: > > From: Matteo Croce > > With this series a monotonically increasing number is added to disks, > precisely in the genhd struct, and it's exported in sysfs and uevent. > > This helps the userspace correlate events for devices that reuse the > same device, like loop. > > The first patch is the core one, the 2..4 expose the information in > different ways, the 5th increases the seqnum on media change and > the last one increases the sequence number for loop devices upon > attach, detach or reconfigure. > > If merged, this feature will immediately used by the userspace: > https://github.com/systemd/systemd/issues/17469#issuecomment-762919781 > Hi Christoph, I just noticed that the series doesn't apply anymore. Before refreshing it, I wish to know what are your opinion on this one, as nobody expressed one on latest submission. -- per aspera ad upstream