Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp5289082pxj; Wed, 26 May 2021 07:16:31 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxo/i0JMOD97wtoRMKdElk6RcMpwKR0lYOfKLVinfnZSh9B+C6nEFY68+OrOtEtyVuFzpDv X-Received: by 2002:a17:906:a96:: with SMTP id y22mr1134134ejf.21.1622038591628; Wed, 26 May 2021 07:16:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1622038591; cv=none; d=google.com; s=arc-20160816; b=eh5GLJTFuq2DrqbOhIqH4Eu03jTntNs9sti2s9EYx2z58l/FwnvSEGdWNPY0xeBB0N JrDC6bwhym3T83rxd3lDX1uomES+5mw5+peiJlE0sberoBZBLk3P/KRtItUT9ZrcEwkg EnPXc1evMoNfUN0vywiKhzAtBu8mRVMoEOsOEeEkzCZM6iZXeVJP5xxogIHl9wVAwHNb 8gpvBfONDvkWeh4G/J2HsZfarlt503V9KoaZe9hxlZ6M8OMIwYtX3kWO8sjHuQOiQJM6 EXsjuYD+/WEpZq/USmaAbKz+soZxoJ4Bbo/Qdf1YwOjCsyj+cNRZWzrmK8c/mZ2rPq8b 6qNw== 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=Hlv5sVjAjS61KZitQI4F9HNXJAk2eb1GHkwnsjqNczM=; b=R1FWwhyelErfwXkvVHefnT0oTc123z9v1PvMfG19StZ+7cPaf02xcJNNHbGtqgpUFB xcFmCUFv7lMUaZ/u99vUaf8ilx1IWGyFg/enrRpWGkDEnabY+zfE3JL0AAmsdLqVsY0L LS4uzOwa6mxvnGoxqu4HFY/fZVsq2atgNAeqb3fm6cI4GQcfp9oAc6REp9oFtU1XFHf2 JgadKK8yvl9NyZ5DOPBR7qGTCyk9yo92XwSLS3EG6fiEmD/5ZTUXbXQVhJ9YsHzpqTUd On3QPz89qBxBJMggclW7dMu+dQx87Qm7qbosHpreAqSQJKpJwCZDopufmVK2TzpYlgct cLMA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux.microsoft.com header.s=default header.b=XijCPxjb; 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 hs11si2116068ejc.609.2021.05.26.07.16.06; Wed, 26 May 2021 07:16:31 -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=XijCPxjb; 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 S234432AbhEZOPc (ORCPT + 99 others); Wed, 26 May 2021 10:15:32 -0400 Received: from linux.microsoft.com ([13.77.154.182]:45408 "EHLO linux.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233484AbhEZOPb (ORCPT ); Wed, 26 May 2021 10:15:31 -0400 Received: from mail-pj1-f47.google.com (mail-pj1-f47.google.com [209.85.216.47]) by linux.microsoft.com (Postfix) with ESMTPSA id 4B95120B8008; Wed, 26 May 2021 07:14:00 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 4B95120B8008 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1622038440; bh=Hlv5sVjAjS61KZitQI4F9HNXJAk2eb1GHkwnsjqNczM=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=XijCPxjbXsVWuQd5w2/NKKrCDn1KFc1qqftWyVwwLldTOLNwQ1VAdsdqSsWs1yuhl +WpTSEF55jXChbTVJiPdsBZ56vXgEKHtLqfGflnoH5SyRHaqRn9mKejgb55jG04WEa aT29+eAbifRmlgC3ORqSqAMc0/MoxlatKxJ+NMFE= Received: by mail-pj1-f47.google.com with SMTP id ne24-20020a17090b3758b029015f2dafecb0so417076pjb.4; Wed, 26 May 2021 07:14:00 -0700 (PDT) X-Gm-Message-State: AOAM5308JhgexHgHV/giY6zLG4ge+TQUzM/2KayeEgJK5zDK9FBNbVkw 1SLDr/HWfMsQICR2Dddp4uMiSiRw7YnqmPrgEgM= X-Received: by 2002:a17:90a:7892:: with SMTP id x18mr3472341pjk.39.1622038439875; Wed, 26 May 2021 07:13:59 -0700 (PDT) MIME-Version: 1.0 References: <20210429102828.31248-1-prasanna.kalever@redhat.com> In-Reply-To: From: Matteo Croce Date: Wed, 26 May 2021 16:13:23 +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 Wed, May 19, 2021 at 4:33 PM Matteo Croce wrote: > > 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 FYI: I just sent a v2 of the diskseq change https://lore.kernel.org/linux-block/20210520135622.44625-1-mcroce@linux.microsoft.com/ -- per aspera ad upstream