From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bedivere.hansenpartnership.com ([66.63.167.143]:45664 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965931AbeFOQJR (ORCPT ); Fri, 15 Jun 2018 12:09:17 -0400 Message-ID: <1529078955.4048.12.camel@HansenPartnership.com> Subject: Re: shiftfs status and future development From: James Bottomley To: Matthew Wilcox , Seth Forshee Cc: containers@lists.linux-foundation.org, Tyler Hicks , Christian Brauner , linux-fsdevel@vger.kernel.org Date: Fri, 15 Jun 2018 09:09:15 -0700 In-Reply-To: <20180615152529.GA23527@bombadil.infradead.org> References: <20180614184448.GC30028@ubuntu-xps13> <20180615135638.GA29299@mail.hallyn.com> <20180615145917.GF30028@ubuntu-xps13> <20180615152529.GA23527@bombadil.infradead.org> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, 2018-06-15 at 08:25 -0700, Matthew Wilcox wrote: > On Fri, Jun 15, 2018 at 09:59:17AM -0500, Seth Forshee wrote: > >  - Supports any id maps possible for a user namespace > > Have we already ruled out storing the container's UID/GID/perms in an > extended attribute, and having all the files owned by the owner of > the container from the perspective of the unshifted fs.  Then shiftfs > reads the xattr and presents the files with the container's idea of > what the UID is? I've got an experimental patch set that does the *mark* as an xattr. However the shift is still done through s_userns, which allows for multiple shifts. James