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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,UNPARSEABLE_RELAY autolearn=no 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 7691FC47082 for ; Tue, 8 Jun 2021 21:42:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6114C610F8 for ; Tue, 8 Jun 2021 21:42:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234692AbhFHVn5 (ORCPT ); Tue, 8 Jun 2021 17:43:57 -0400 Received: from nautica.notk.org ([91.121.71.147]:37908 "EHLO nautica.notk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234344AbhFHVnz (ORCPT ); Tue, 8 Jun 2021 17:43:55 -0400 X-Greylist: delayed 165346 seconds by postgrey-1.27 at vger.kernel.org; Tue, 08 Jun 2021 17:43:55 EDT Received: by nautica.notk.org (Postfix, from userid 108) id 3FB5CC022; Tue, 8 Jun 2021 23:42:00 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codewreck.org; s=2; t=1623188520; bh=BzT3wyhqpB6185zh00HzeGjst0xNZzNRNRcMkS0h4Ek=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=TPCVJJPheMdSOTumApcB7X+1E/NcOwTUaPkWOc0lpWofraySQuqK/Fcz1QR6mNJu/ JbIBKs/drSoZzxeIaf8DU0tcv9YgrMNiR9LgzEx5Jp9SRNagHzDD3i7zi+FOEo/XNJ PbSCFfPCoCcvdEbuB9SHmSId3kCsa3A9i6hzSXy45RUsscxetLrLqsMCTUaNMm49UN bwYG+NWjh/K8BEQOhSdGCCVa17ZOAdaJ6qeDg+T+pKZf2Yhee13uQc7YW8WObvi3GL 70AEi/UPGVfR2Jv2x6K94NNblVioAzUPYNkVqPqAoBESmnu/nAN5SlJ3uRurgWzvvm BCngHHHE4/VLg== Received: from odin.codewreck.org (localhost [127.0.0.1]) by nautica.notk.org (Postfix) with ESMTPS id B5FE2C01A; Tue, 8 Jun 2021 23:41:55 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codewreck.org; s=2; t=1623188519; bh=BzT3wyhqpB6185zh00HzeGjst0xNZzNRNRcMkS0h4Ek=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=hZs7zDSzWVrirXlYRkb+jr8ZfGHEWgLxIP6E4ym/fYo38OHCnrgAXLk03GvlJ80wc x4mK1vQ5pH8UOHFvd8L4zqag2eWJnnMdHYfznLUafJ+oP8csmM21fusFJhPGd2IHMP x2A+h/66ugFwS/ecXQDBFnfvvyZGsFSNO6ofK0bLXiyzQARFG4DcbZyQFti3B4i1my A1JVbDm/2VNinrbZODsGhJfERVUeNRvAsCBcacT/cJA9HGmH/LIBAiFl42Et7hhdXk NDJ/fB7kpmf30DKYvH2PI4iaXRNGopmekboUxPqkpuDH/pgxlmDD+K+kI4L1avIiaK H/hT4xQFNqKGw== Received: from localhost (odin.codewreck.org [local]) by odin.codewreck.org (OpenSMTPD) with ESMTPA id 4cf7185a; Tue, 8 Jun 2021 21:41:53 +0000 (UTC) Date: Wed, 9 Jun 2021 06:41:38 +0900 From: Dominique Martinet To: Vivek Goyal , Changbin Du Cc: linux-fsdevel@vger.kernel.org, virtio-fs@redhat.com, linux kernel mailing list , Miklos Szeredi , David Howells , viro@zeniv.linux.org.uk, stefanha@redhat.com, Richard Weinberger , dgilbert@redhat.com, v9fs-developer@lists.sourceforge.net, Enrico Weigelt Subject: Re: [PATCH] init/do_mounts.c: Add root="fstag:" syntax for root device Message-ID: References: <20210608153524.GB504497@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210608153524.GB504497@redhat.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ... And that's why I told Changbin Du a few times his patches needed more Ccs :/ FWIW: we just got last month a couple of patches that would allow initrd-less 9p root mount (using the nfs/cifs method described below with root=/dev/v9fs) Vivek Goyal wrote on Tue, Jun 08, 2021 at 11:35:24AM -0400: > NFS and CIFS use "root=/dev/nfs" and CIFS passes "root=/dev/cifs" and > actual root device details come from filesystem specific kernel > command line options. > > virtiofs does not seem to fit in any of the above categories. In fact > we have 9pfs which can be used to boot from but it also does not > have a proper syntax to specify rootfs and does not fit into any of > the existing syntax. They both expect a device "tag" to be passed > in a device to be mounted. And filesystem knows how to parse and > use "tag". > > So this patch proposes that we add a new prefix "fstag:" which specifies > that identifier which follows is filesystem specific tag and its not > a block device. Just pass this tag to filesystem and filesystem will > figure out how to mount it. ...However I agree something more generic would be welcome in my opinion, so I like this approach. I'll give it a try for 9p over the weekend and report back. -- Dominique