Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp78136ybb; Tue, 14 Apr 2020 19:27:27 -0700 (PDT) X-Google-Smtp-Source: APiQypI3ZKQK0m+Guh/lQoGLsOFTi90ywwRv9bDIjgZRJBKo4H7dGrtEiRxHbwoQklWXi4Jjf6qN X-Received: by 2002:aa7:c352:: with SMTP id j18mr5363888edr.196.1586917647340; Tue, 14 Apr 2020 19:27:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586917647; cv=none; d=google.com; s=arc-20160816; b=RGWIVZzpp+ljV+apQZEjA+7Tr6dwkJ8grIBGT2s44RgZwnvblQ59hTqp9fCYCkmpaX ZVfdWcwlmTyyGFUBZAXoCJ9Uo6GMKYp5jddp4NpwO3QHhmcW8mqXCoMMOlo+Fs3YEGct FpTlpznKoCBgGlhFNUhez0gJi0fJjKsU0rIdb73ty+NNCQP5Q/cjw6WYnXHG6xV1S+ZX 2w9z5qPkea7K/rpZfoi2bkO+Zg7Ewx55DDVyKgjIkZEc6/yWjWDmX1ZYpoAI1q6W20PB NRWX2KVxjpf9tIj8tFNgqFp7+WFWgOXI1cQJDa/mUfI4MloRX9gN+7R9JDKXs7ylKULN F+zA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=rva10rUQIawf/X7fczPayHayLk00s/sKsp8QYGFsjYc=; b=Nfp0GbotiP5ulqZMELW7+PezXEM2ggbUMa5ojpPsG5K24NpAGxp1kcNbIqaAa4Iiog SOIo1Sn1QAdrPnas6z7pel6L+ZUna6iUNz2ff1dmd8FEMGssy8NuRY6b4mqFaDsHAtnM Q0IG+S4PqS7S3cJRxnVDyBii0f+XNXcrytAu5qAY3tuqZP2iNode8Plh1VtzUn0b1/dt 6hKdVSNM7JuH16fEhuoeOWHA+mTGnSF809eGVzGHkF6t339+dY74vXshThRzkTM7YLXB A0Bvm351IPyUnCJ/L9C7EZIz7JVm/w9kbkImPbTomN92uDVemUlMmGOhgCMqqP8rvHoA XHmw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for 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 i19si9027521edr.235.2020.04.14.19.27.00; Tue, 14 Apr 2020 19:27:27 -0700 (PDT) Received-SPF: pass (google.com: best guess record for 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: best guess record for 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 S2388017AbgDMTmX (ORCPT + 99 others); Mon, 13 Apr 2020 15:42:23 -0400 Received: from youngberry.canonical.com ([91.189.89.112]:45382 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387935AbgDMTmW (ORCPT ); Mon, 13 Apr 2020 15:42:22 -0400 Received: from ip5f5bd698.dynamic.kabel-deutschland.de ([95.91.214.152] helo=wittgenstein) by youngberry.canonical.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.86_2) (envelope-from ) id 1jO4yJ-0002rq-Iv; Mon, 13 Apr 2020 19:42:19 +0000 Date: Mon, 13 Apr 2020 21:42:18 +0200 From: Christian Brauner To: Tejun Heo Cc: Jens Axboe , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, linux-api@vger.kernel.org, Jonathan Corbet , Serge Hallyn , "Rafael J. Wysocki" , "David S. Miller" , Saravana Kannan , Jan Kara , David Howells , Seth Forshee , David Rheinsberg , Tom Gundersen , Christian Kellner , Dmitry Vyukov , =?utf-8?B?U3TDqXBoYW5l?= Graber , linux-doc@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH 6/8] genhd: add minimal namespace infrastructure Message-ID: <20200413194218.trqz3362k4y2v7ob@wittgenstein> References: <20200408152151.5780-1-christian.brauner@ubuntu.com> <20200408152151.5780-7-christian.brauner@ubuntu.com> <20200413190452.GH60335@mtj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20200413190452.GH60335@mtj.duckdns.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 13, 2020 at 03:04:52PM -0400, Tejun Heo wrote: > Hello, > > On Wed, Apr 08, 2020 at 05:21:49PM +0200, Christian Brauner wrote: > > This lets the block_class properly support loopfs device by introducing > > the minimal infrastructure needed to support different sysfs views for > > devices belonging to the block_class. This is similar to how network > > devices work. Note, that nothing changes with this patch since > > I was hoping that all devices on the system would be visible at the root level > as administration at system level becomes pretty tricky otherwise. Is it just > me who thinks this way? Hey Tejun, I think this is the same question in a different form you had in https://lore.kernel.org/lkml/20200413193950.tokh5m7wsyrous3c@wittgenstein/T/#m20b396a29c8d499d9dc073e6aef38f38c08f8bbe and I tried answered it there. Thanks! Christian