From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 888E3A0032; Fri, 24 Jun 2022 15:37:38 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 278324069D; Fri, 24 Jun 2022 15:37:38 +0200 (CEST) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by mails.dpdk.org (Postfix) with ESMTP id 1F5A1400EF for ; Fri, 24 Jun 2022 15:37:35 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1656077856; x=1687613856; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=OPmuEikep81Xqa5JUHju3HqjpZXGsqPxlv/0/C+G+qY=; b=YPL3RPzNbLSgFWI4oMgFSfqckwpETaa24AHZTTRaAaXlPNa/IAAgxltZ ACjrFriCa1hGUXK7Q9QVJg2JaOQ0SK9yd/vWS8YjZGFRpk+s5Owd9+uy2 3/z5GFDUvYTQhi1ViTOKVXVNQVaRC0fZOaZ9QMY/KL8Icf/SCvnYqr6ld UubLnsHijEb4Yklvv18575KWqBUAPx8fs8lM4yLcHdH2NR9JU7uFY8KJT ahCeYQtKlqkOcw30qk3KmpwHnKmXzjvQKgoMdpGZvsg8hR6q6aL51v5by vJaJ5wDJ86H7MxEvBbOi1odYkD98vDmLls8gW8q3AYdPuFuO9FQyhvSDh Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10387"; a="261426233" X-IronPort-AV: E=Sophos;i="5.92,218,1650956400"; d="scan'208";a="261426233" Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Jun 2022 06:37:33 -0700 X-IronPort-AV: E=Sophos;i="5.92,218,1650956400"; d="scan'208";a="656647442" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.25.171]) by fmsmga004-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 24 Jun 2022 06:37:31 -0700 Date: Fri, 24 Jun 2022 14:37:28 +0100 From: Bruce Richardson To: Dmitry Kozlyuk Cc: dev@dpdk.org Subject: Re: [PATCH v4 2/5] usertools: add options to change mount point owner Message-ID: References: <20220624084817.63145-1-dkozlyuk@nvidia.com> <20220624131956.75160-1-dkozlyuk@nvidia.com> <20220624131956.75160-3-dkozlyuk@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220624131956.75160-3-dkozlyuk@nvidia.com> X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Fri, Jun 24, 2022 at 04:19:53PM +0300, Dmitry Kozlyuk wrote: > Per mount(8), the previous owner and mode of the mount point > become invisible as long as this filesystem remains mounted. > Because dpdk-hugepages.py must be run as root, > the new owner would be root. > This is undesirable if the hugepage directory is being set up > by the administrator for an unprivileged user. > HugeTLB filesystem has options to set the mount point owner. > Add --user/-U and --group/-G options to apply this when mounting. > The benefit of performing this in dpdk-hugepages.py > is that the user does not need to care about this detail > of mount command operation. > > Signed-off-by: Dmitry Kozlyuk > --- Acked-by: Bruce Richardson