Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1753709pxj; Wed, 19 May 2021 13:07:48 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwOxyv3Epq+QfH4rxk3Ux3KaGl04qNW8D6wymilZQsWGhCFarlpgalST4ZUwNgLZVv3WobT X-Received: by 2002:a05:6402:4313:: with SMTP id m19mr783877edc.263.1621454868132; Wed, 19 May 2021 13:07:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621454868; cv=none; d=google.com; s=arc-20160816; b=QF04xenIaYfrp6M86I+4t+K/ziOtaVBo2zx60+EudclqN/bkwE+QVZOwcvb77p2ADW fYHgIfWpB8dffVtAIN3jcvladI+dcJivHqZZJzKuVk0Gxyt6LkqyeEdT7U94yjEBDZU0 qj+IiBgQm1xfGMLkbeQyDxLocpEZw6VnP3f0Y6JXVsTlBv97Ena2w+PoWIHFeECA/iuf v+83FZvD31GPCNVcSZWnpwEaN+0AtAXMt4sfFgUmmGITSMxbBPHp0wavMQrjngrcvulW ttMd5awTPKArTcg5hvWf2liR3TWxTUPZnInkWfE9n0Q9PSokRjbxJ2hp1k4GrZByYvuo ayRw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature:dkim-filter; bh=2l115mN3zp/dArufLuzm7XoNobdsZKeT527UpaHVKJg=; b=ZwzKEKfuJwJp6bNSPR/i4KnpD8l/iUUODHld/tocckbwYmqczPh6HA2jCq7zl8b6OD 5x8aW+wPv2ypIR61YnLYKfT5ofvirOC0MsjJxxhaFZWTy/UnC7cb/Qrcrh8hjaEdl0EQ I9UEoJnMqVUgYRK4OPuMzbRQ2tXJXR6tI9t6HJa8BEzfr67AdsefxJIH5k0EsT50rA8+ kMT9J3O2WiQ5cEaqM3w3491JFAw+/b19ZUTvsLl0X2ezAa7+G7k0Jm9uldJDmNP72iVj BIgb579q5lqNdMz2iaagb4nZOdeXNKrDawfqKELH8oGT/Z69A9D61+c1T0zlBIGTOXwG xHuQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux.microsoft.com header.s=default header.b=fHKdSAd+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.microsoft.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id de51si603623ejc.406.2021.05.19.13.07.23; Wed, 19 May 2021 13:07:48 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linux.microsoft.com header.s=default header.b=fHKdSAd+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.microsoft.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241791AbhESOfS (ORCPT + 99 others); Wed, 19 May 2021 10:35:18 -0400 Received: from linux.microsoft.com ([13.77.154.182]:57946 "EHLO linux.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240366AbhESOfQ (ORCPT ); Wed, 19 May 2021 10:35:16 -0400 Received: from mail-pf1-f171.google.com (mail-pf1-f171.google.com [209.85.210.171]) by linux.microsoft.com (Postfix) with ESMTPSA id DFBA820B8008; Wed, 19 May 2021 07:33:56 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com DFBA820B8008 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1621434836; bh=2l115mN3zp/dArufLuzm7XoNobdsZKeT527UpaHVKJg=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=fHKdSAd+bIMDIFjv1VQkygdXDbeaC76BtcOvxnUrwzT9tEtt8qayiqhuCexkqQGOK vSAeVfPQl2TAKTE5yuSQ6xYUIwPThjO8oTXU/LXOxBqCjTfPdYvqTKkbW6eqrsmzVV UOQ/VStej2fWyctME1BSAc/c+X5oiKJC/CTgFDTs= Received: by mail-pf1-f171.google.com with SMTP id x18so5734227pfi.9; Wed, 19 May 2021 07:33:56 -0700 (PDT) X-Gm-Message-State: AOAM530aS1uONyRJsUUanXoKcNVAX8aOFv9kkhsO5h7JAiI8/0rUO2sp 4MUy4XXTi9nYmMDFLP29UpD+fSGI6K6TDHvK4Fg= X-Received: by 2002:aa7:9f5c:0:b029:2de:a5f0:d73b with SMTP id h28-20020aa79f5c0000b02902dea5f0d73bmr7960822pfr.41.1621434836421; Wed, 19 May 2021 07:33:56 -0700 (PDT) MIME-Version: 1.0 References: <20210429102828.31248-1-prasanna.kalever@redhat.com> In-Reply-To: From: Matteo Croce Date: Wed, 19 May 2021 16:33:19 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] nbd: provide a way for userspace processes to identify device backends To: Prasanna Kalever Cc: Ming Lei , Prasanna Kumar Kalever , linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, nbd@other.debian.org, Josef Bacik , Jens Axboe , Ilya Dryomov , Xiubo Li , Lennart Poettering , Luca Boccassi Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 18, 2021 at 9:52 AM Prasanna Kalever wrote: > > BTW, loop has similar issue, and patch of 'block: add a sequence number to disks' > > is added for addressing this issue, what do you think of that generic > > approach wrt. this nbd's issue? such as used the exposed sysfs sequence number > > for addressing this issue? > > > > https://lore.kernel.org/linux-block/YH81n34d2G3C4Re+@gardel-login/#r > > If I understand the changes and the background of the fix correctly, I > think with that fix author is trying to monotonically increase the seq > number and add it to the disk on every single device map/attach and > expose it through the sysfs, which will help the userspace processes > further to correlate events for particular and specific devices that > reuse the same loop device. > Yes, but nothing prevents to use diskseq in nbd, and increase it on reconfigure. That would allow to detect if the device has been reconfigured. Regards, -- per aspera ad upstream