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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D2172C001B0 for ; Sat, 24 Jun 2023 01:37:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231770AbjFXBh5 (ORCPT ); Fri, 23 Jun 2023 21:37:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58446 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229543AbjFXBhz (ORCPT ); Fri, 23 Jun 2023 21:37:55 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9077BE41 for ; Fri, 23 Jun 2023 18:37:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1687570630; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SWrf17db78ezE6/aH1TL74NU60boy/nUbrBlOEfT/sU=; b=hMclPX1M8U+zpt+kUJc30oAJaKRydBzPfTNyaZQ32GCqNSON1J5iSfRPSJlAnFW6qkY2la 87VYSk5gIRhtRj6Z4VxvTcTFj2CTi8I76mjutifaKDaDxTDQ+bXowQJo3aXo9zcuoFRu5/ ryW/qDFqsoiL6EiHrhGN/v4Ml+TiDLA= Received: from mail-pl1-f200.google.com (mail-pl1-f200.google.com [209.85.214.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-10-zYplhiXuO-ePdvlryXopZA-1; Fri, 23 Jun 2023 21:37:09 -0400 X-MC-Unique: zYplhiXuO-ePdvlryXopZA-1 Received: by mail-pl1-f200.google.com with SMTP id d9443c01a7336-1b5381523bcso8872855ad.0 for ; Fri, 23 Jun 2023 18:37:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687570628; x=1690162628; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:subject:from:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=SWrf17db78ezE6/aH1TL74NU60boy/nUbrBlOEfT/sU=; b=OZzepKEhdDnliifRA2GQ1Uy+9RS+jeiQnVT6E/577XFvUV+X8HY8LFf9CrksMplXWK q/A8JGB5DNhjvVICJIF475f4E4vjhYdIQUBkWBqHI887khIxaoO5REwqqPCh8NzfOgi7 QYDntGy0B12JyJDnhEHp9nxQcbsgsZsu6JrxRjuVb1EBmYqwHvs6o5crT/TMqtwi0fw3 P14PORPF/HAk0754V6cnaxUj+Ps9prRjb/9s9BQTiqeoY1XzrO58A0EACWMSgiJnDOFJ VS7u+/rEiR58VUvRYu5jCVHv/LAunfAKHziDiI8Nrc+bccAK209WC01OFpFzOKY3mGDN nZHw== X-Gm-Message-State: AC+VfDyxSm2XSxbn7Z81IoRq+AnYGU7VJI4ajzBeLlEYDLuotPVKimMm +OqfVonw4TQDMDouJyWqNqqZZMZb14QgrCxyuyqenVSmnfizaCFiZzaN941Bdb0+qHD/70dN6vw Zg9bLmQApxgldUk5Zzy5AtkVH X-Received: by 2002:a17:903:24d:b0:1ae:8595:153 with SMTP id j13-20020a170903024d00b001ae85950153mr1087403plh.20.1687570628103; Fri, 23 Jun 2023 18:37:08 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ70F87Rbv/R9XMaSzZcQtw3TRpiFahOhZs33X4KSJY20FL+t3G4c1wHrNU4qH+U5MgkwpyEHA== X-Received: by 2002:a17:903:24d:b0:1ae:8595:153 with SMTP id j13-20020a170903024d00b001ae85950153mr1087385plh.20.1687570627829; Fri, 23 Jun 2023 18:37:07 -0700 (PDT) Received: from [10.72.12.106] ([209.132.188.80]) by smtp.gmail.com with ESMTPSA id gf4-20020a17090ac7c400b00256dff5f8e3sm259169pjb.49.2023.06.23.18.37.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 23 Jun 2023 18:37:07 -0700 (PDT) Message-ID: <64241ff0-9af3-6817-478f-c24a0b9de9b3@redhat.com> Date: Sat, 24 Jun 2023 09:36:54 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 From: Xiubo Li Subject: Re: [PATCH v5 00/14] ceph: support idmapped mounts To: Aleksandr Mikhalitsyn Cc: Gregory Farnum , Christian Brauner , stgraber@ubuntu.com, linux-fsdevel@vger.kernel.org, Ilya Dryomov , Jeff Layton , ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org References: <20230608154256.562906-1-aleksandr.mikhalitsyn@canonical.com> <20230609-alufolie-gezaubert-f18ef17cda12@brauner> <977d8133-a55f-0667-dc12-aa6fd7d8c3e4@redhat.com> <626175e2-ee91-0f1a-9e5d-e506aea366fa@redhat.com> Content-Language: en-US In-Reply-To: <626175e2-ee91-0f1a-9e5d-e506aea366fa@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [...] > > > > > > I thought about this too and came to the same conclusion, that UID/GID > > > based > > > restriction can be applied dynamically, so detecting it on mount-time > > > helps not so much. > > > > > For this you please raise one PR to ceph first to support this, and in > > the PR we can discuss more for the MDS auth caps. And after the PR > > getting merged then in this patch series you need to check the > > corresponding option or flag to determine whether could the idmap > > mounting succeed. > > I'm sorry but I don't understand what we want to support here. Do we want to > add some new ceph request that allows to check if UID/GID-based > permissions are applied for > a particular ceph client user? IMO we should prevent user to set UID/GID-based permisions caps from ceph side. As I know currently there is no way to prevent users to set MDS auth caps, IMO in ceph side at least we need one flag or option to disable this once users want this fs cluster sever for idmap mounts use case. Thanks - Xiubo