From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751690AbdBOJmy (ORCPT ); Wed, 15 Feb 2017 04:42:54 -0500 Received: from out01.mta.xmission.com ([166.70.13.231]:36226 "EHLO out01.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751445AbdBOJmY (ORCPT ); Wed, 15 Feb 2017 04:42:24 -0500 From: ebiederm@xmission.com (Eric W. Biederman) To: Djalal Harouni Cc: James Bottomley , Josh Triplett , Christoph Hellwig , Amir Goldstein , Chris Mason , Theodore Tso , Andy Lutomirski , Seth Forshee , linux-fsdevel , linux-kernel , LSM List , Dongsu Park , David Herrmann , Miklos Szeredi , Alban Crequy , Al Viro , "Serge E. Hallyn" , Phil Estes References: <1486235880.2484.17.camel@HansenPartnership.com> <1486235972.2484.19.camel@HansenPartnership.com> <20170207091924.GA13995@infradead.org> <1486485440.2488.15.camel@HansenPartnership.com> <20170207181040.GA18551@infradead.org> <1486494123.2488.56.camel@HansenPartnership.com> <20170207194933.GB4393@infradead.org> <20170208015423.GC23245@cloud> <1486567365.2484.28.camel@HansenPartnership.com> <20170209103640.myuysvawpj55z4fi@x> <1486654467.2616.8.camel@HansenPartnership.com> <87poim75wr.fsf@xmission.com> Date: Wed, 15 Feb 2017 22:37:41 +1300 In-Reply-To: (Djalal Harouni's message of "Wed, 15 Feb 2017 10:33:53 +0100") Message-ID: <8760kbg5ga.fsf@xmission.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-XM-SPF: eid=1cdw6I-0006yq-JB;;;mid=<8760kbg5ga.fsf@xmission.com>;;;hst=in02.mta.xmission.com;;;ip=101.100.131.232;;;frm=ebiederm@xmission.com;;;spf=neutral X-XM-AID: U2FsdGVkX1+j2tajgBDmKCga5V5g+h3qyGAAySCiTRc= X-SA-Exim-Connect-IP: 101.100.131.232 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * 1.5 XMNoVowels Alpha-numberic number with no vowels * 0.0 T_TM2_M_HEADER_IN_MSG BODY: No description available. * 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% * [score: 0.4990] * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa04 1397; Body=1 Fuz1=1 Fuz2=1] * 1.2 XMSubMetaSxObfu_03 Obfuscated Sexy Noun-People * 1.0 XMSubMetaSx_00 1+ Sexy Words X-Spam-DCC: XMission; sa04 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ***;Djalal Harouni X-Spam-Relay-Country: X-Spam-Timing: total 5694 ms - load_scoreonly_sql: 0.06 (0.0%), signal_user_changed: 4.0 (0.1%), b_tie_ro: 2.6 (0.0%), parse: 1.46 (0.0%), extract_message_metadata: 25 (0.4%), get_uri_detail_list: 2.2 (0.0%), tests_pri_-1000: 12 (0.2%), tests_pri_-950: 1.59 (0.0%), tests_pri_-900: 1.31 (0.0%), tests_pri_-400: 26 (0.5%), check_bayes: 25 (0.4%), b_tokenize: 10 (0.2%), b_tok_get_all: 8 (0.1%), b_comp_prob: 2.4 (0.0%), b_tok_touch_all: 2.9 (0.1%), b_finish: 0.73 (0.0%), tests_pri_0: 278 (4.9%), check_dkim_signature: 0.89 (0.0%), check_dkim_adsp: 4.3 (0.1%), tests_pri_500: 5340 (93.8%), poll_dns_idle: 5331 (93.6%), rewrite_mail: 0.00 (0.0%) Subject: Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount X-Spam-Flag: No X-SA-Exim-Version: 4.2.1 (built Thu, 05 May 2016 13:38:54 -0600) X-SA-Exim-Scanned: Yes (on in02.mta.xmission.com) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Djalal Harouni writes: > On Mon, Feb 13, 2017 at 11:15 AM, Eric W. Biederman > wrote: >> James Bottomley writes: >>> So is this. Basically anything that begins by mounting gets a super >>> block and can use the s_user_ns to map from the filesystem view to the >>> kernel view of ids. Apart from greater sophistication in the >>> parametrisation, it sounds like we have all the machinery you need. >>> I'm sure the containers people will consider reasonable patches to >>> change this. >> >> Yes. >> >> And to be clear we have all of that merged now and mostly present and >> hooked up in all filesystems without any shiftfs like changes needed. >> >> To use this with a filesystem a last pass needs to be had to verify that >> the cases where something does not map are handled cleanly. > > Still this does not answer the question how to dynamically > *attach/share* data or read-only volumes as defined by > orchestration/container tools into several containers. Am I missing > something or is the plan to have per superblock mount for each one ? Agreed. That is a related problem and the problem that shiftfs is working to solve. If you only need a single mapping the infrastructure is basically done in the kernel today. If you need multiple mappings we need something more. Eric