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 Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1E42BC25B0C for ; Tue, 9 Aug 2022 18:14:27 +0000 (UTC) Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4M2LnF4M5Yz30Qc for ; Wed, 10 Aug 2022 04:14:25 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=t7GJvmBD; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=kernel.org (client-ip=139.178.84.217; helo=dfw.source.kernel.org; envelope-from=xiang@kernel.org; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=t7GJvmBD; dkim-atps=neutral Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4M2Ln6008Kz2xKh for ; Wed, 10 Aug 2022 04:14:17 +1000 (AEST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 1D43F61139; Tue, 9 Aug 2022 18:14:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0539FC433D6; Tue, 9 Aug 2022 18:14:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1660068853; bh=KwXhJdbDx5tMFFVQpOxN5q2eUYWE2D5mzNx6+CMbCWc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=t7GJvmBD0AKjFMERLerSligtWDvpVlAUcZuH0GstCBo231C/wFHMcIxGGNbNdG14Y OkA19wTuM4UHJrDz3TIPEVILatOwxkm1XScFGTmAVhVqRy7DE/cNfjKw4ssmuMYak4 SdMbZZ7drC5Ejo0EO/JuEt0iKACn0xADfmy/TYthqLpiepV07ACoEzqePIbwf4QA7P OFTiB7ngO4v887jluR8F0LmtfUrR908XEhHFJna7qEWzasYLGNSL7lVYwHJ2DDRalp FitZ/5MCFG4pFqvVEoSjNtmo8IdvtFPEZ1qLc4cHedZXnKn6EiXGwZ4zugGe1Fwel4 v/c6JCeMZ0xWw== Date: Wed, 10 Aug 2022 02:14:09 +0800 From: Gao Xiang To: Naoto Yamaguchi Subject: Re: RFC: erofs-utils:mkfs: add unprivileged container use-case support Message-ID: Mail-Followup-To: Naoto Yamaguchi , linux-erofs@lists.ozlabs.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-BeenThere: linux-erofs@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development of Linux EROFS file system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-erofs@lists.ozlabs.org Errors-To: linux-erofs-bounces+linux-erofs=archiver.kernel.org@lists.ozlabs.org Sender: "Linux-erofs" Hi Naoto, On Wed, Aug 10, 2022 at 02:59:42AM +0900, Naoto Yamaguchi wrote: > Hi all. > > I investigate each read only filesystem for linux at linux container > use-case. The erofs is most interesting filesystem. First of all, many thanks for your interest! Yes, now EROFS is actively developing for container use cases as well, and we're happy to accept/maintain any useful features about this area! > A each files of guest root filesystem need to shift uid/gid in case of > unprivileged container to use uid/gid namespace. I work adding > uid/gid offsetting support to erofs-utils mkfs tool now. > Will be this patch accept in upstream community? Could you give more details about this? EROFS already supports idmapped mount for container use cases since 5.19, so I guess uid/gid offsets can be set by this? I'm still somewhat new to container world, it would be helpful to drop more hints of this ;) Thanks, Gao Xiang > > Thanks, > Naoto Yamaguchi, > a member of Automotive Grade Linux Instrument Cluster EG.