Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1396132pxj; Fri, 21 May 2021 13:12:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwwgQkGV5371FBoXpwgDUGt5mDV1kUGGxV6Sz9PGGlUWtMJqUrbiOuPrgEKviVkvTzVPROH X-Received: by 2002:a6b:6704:: with SMTP id b4mr567203ioc.123.1621627946873; Fri, 21 May 2021 13:12:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621627946; cv=none; d=google.com; s=arc-20160816; b=pDgQ4sMroDMkwTegi2C8UfpVck2XmnSfzm1+eVI/Zul66LUzw8b6AQktD1AmdjOZZp 7FG6eO5vkLYmz3dnG1zohscDzhUpe4k0EvVx1TpxFC7d4kY9/MzFTyCvGyz1Yb44GVuh iMVF7NNgEgWd5nMQ7A3pCvuFAyF0Kat0JKwukkHkXlU3mN443n0n9QtafQO2I9nAReWH faAxuErLOy5R8edjUZT4c49MH8clUIadU6z6HeMxfO6DZaM4Gj4h2DrpSB7uecOSnKf+ pKDQPjzgtPNP3QI2TfIbefkIrf3ssRbln5mpljcW3d7HHnsvz5sDPEdj/HaEWRqoyKmA Jb8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=FLyRtZg73sc/Rxhp2SvS951Wn7iWMKcdDAhr6muY6r8=; b=sKrgrMbrcqVPilMi7IoB2EJsFF3jZJfSnhn4+W+CFDFAwmaP8z3YRD6vkKG/O+nzFN CdHjdHVBn57+fofvWrK34Xza7OIWkGndY/gjpi5Cuk3iauJHAtz+57SqvWG4iqt+9NaE XcV9qsmRwFd79mZvUAEiKEdjWLdyDgZ2jOmPKxjt3zAlInbrd9zDPUatf4gZ29Fk2E6d B+clxaQi3kZD+htahKEk60bJirEM8q9UU72RZXVXiAKBbJh7vM7esv4u+u60faWugeDU Q1q6HBIwVA5STJYVqPUPkpSpGzcJ/4rWEVE70NL6quIYKZLBOt0Ido3n/unhiIRHGsnZ T8Mg== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x17si6781583jan.4.2021.05.21.13.12.14; Fri, 21 May 2021 13:12:26 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233739AbhEUKIM convert rfc822-to-8bit (ORCPT + 99 others); Fri, 21 May 2021 06:08:12 -0400 Received: from us-smtp-delivery-44.mimecast.com ([207.211.30.44]:23308 "EHLO us-smtp-delivery-44.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233631AbhEUKIC (ORCPT ); Fri, 21 May 2021 06:08:02 -0400 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-321-nzPTwh8TNoKqhAUNAmkdWg-1; Fri, 21 May 2021 06:06:33 -0400 X-MC-Unique: nzPTwh8TNoKqhAUNAmkdWg-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 703E56D241; Fri, 21 May 2021 10:06:32 +0000 (UTC) Received: from bahia.lan (ovpn-112-49.ams2.redhat.com [10.36.112.49]) by smtp.corp.redhat.com (Postfix) with ESMTP id CFCBB1964B; Fri, 21 May 2021 10:06:17 +0000 (UTC) Date: Fri, 21 May 2021 12:06:16 +0200 From: Greg Kurz To: Miklos Szeredi Cc: virtualization@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, virtio-fs-list , Stefan Hajnoczi , Max Reitz , Vivek Goyal Subject: Re: [PATCH v4 4/5] virtiofs: Skip submounts in sget_fc() Message-ID: <20210521120616.49d52565@bahia.lan> In-Reply-To: References: <20210520154654.1791183-1-groug@kaod.org> <20210520154654.1791183-5-groug@kaod.org> <20210521103921.153a243d@bahia.lan> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: kaod.org Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: 8BIT Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 21 May 2021 10:50:34 +0200 Miklos Szeredi wrote: > On Fri, 21 May 2021 at 10:39, Greg Kurz wrote: > > > > On Fri, 21 May 2021 10:26:27 +0200 > > Miklos Szeredi wrote: > > > > > On Thu, 20 May 2021 at 17:47, Greg Kurz wrote: > > > > > > > > All submounts share the same virtio-fs device instance as the root > > > > mount. If the same virtiofs filesystem is mounted again, sget_fc() > > > > is likely to pick up any of these submounts and reuse it instead of > > > > the root mount. > > > > > > > > On the server side: > > > > > > > > # mkdir ${some_dir} > > > > # mkdir ${some_dir}/mnt1 > > > > # mount -t tmpfs none ${some_dir}/mnt1 > > > > # touch ${some_dir}/mnt1/THIS_IS_MNT1 > > > > # mkdir ${some_dir}/mnt2 > > > > # mount -t tmpfs none ${some_dir}/mnt2 > > > > # touch ${some_dir}/mnt2/THIS_IS_MNT2 > > > > > > > > On the client side: > > > > > > > > # mkdir /mnt/virtiofs1 > > > > # mount -t virtiofs myfs /mnt/virtiofs1 > > > > # ls /mnt/virtiofs1 > > > > mnt1 mnt2 > > > > # grep virtiofs /proc/mounts > > > > myfs /mnt/virtiofs1 virtiofs rw,seclabel,relatime 0 0 > > > > none on /mnt/mnt1 type virtiofs (rw,relatime,seclabel) > > > > none on /mnt/mnt2 type virtiofs (rw,relatime,seclabel) > > > > > > > > And now remount it again: > > > > > > > > # mount -t virtiofs myfs /mnt/virtiofs2 > > > > # grep virtiofs /proc/mounts > > > > myfs /mnt/virtiofs1 virtiofs rw,seclabel,relatime 0 0 > > > > none on /mnt/mnt1 type virtiofs (rw,relatime,seclabel) > > > > none on /mnt/mnt2 type virtiofs (rw,relatime,seclabel) > > > > myfs /mnt/virtiofs2 virtiofs rw,seclabel,relatime 0 0 > > > > # ls /mnt/virtiofs2 > > > > THIS_IS_MNT2 > > > > > > > > Submount mnt2 was picked-up instead of the root mount. > > > > > > > > Why is this a problem? > > > > > > > It seems very weird to mount the same filesystem again > > and to end up in one of its submounts. We should have: > > > > # ls /mnt/virtiofs2 > > mnt1 mnt2 > > Okay, sorry, I understand the problem. The solution is wrong, > however: the position of the submount on that list is no indication > that it's the right one (it's possible that the root sb will go away > and only a sub-sb will remain). > Ah... I had myself convinced this could not happen, i.e. you can't unmount a parent sb with a sub-sb still mounted. How can this happen ? > Even just setting a flag in the root, indicating that it's the root > isn't fully going to solve the problem. > > Here's issue in full: > > case 1: no connection for "myfs" exists > - need to create fuse_conn, sb > > case 2: connection for "myfs" exists but only sb for submount How would we know this sb isn't a root sb ? > - only create sb for root, reuse fuse_conn > > case 3: connection for "myfs" as well as root sb exists > - reuse sb > > I'll think about how to fix this properly, it's probably going to be > rather more involved... > Sure. BTW I'm wondering why we never reuse sbs for submounts ? > Thanks, > Miklos