Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20221129103949.19737-1-lhenriques@suse.de> <4914a195-edc0-747b-6598-9ac9868593a1@redhat.com>
 <CAOi1vP8raoFP2dsc6RY1fONCsHh5FYv2xifFY7pHXZWX=-vePw@mail.gmail.com>
 <20e0674a-4e51-a352-9ce2-d939cd4f3725@redhat.com> <CAOi1vP_H8jE4ZU4a4srhQev3odECgZD1LyxA8dv+Fk-bVDvoyQ@mail.gmail.com>
In-Reply-To: <CAOi1vP_H8jE4ZU4a4srhQev3odECgZD1LyxA8dv+Fk-bVDvoyQ@mail.gmail.com>
From:   Gregory Farnum <gfarnum@redhat.com>
Date:   Tue, 29 Nov 2022 22:54:38 -0800
Message-ID: <CAJ4mKGb=_CWTh5rrAFiib66-S6WeT=ajjkN_pOAac4d8uC9fDQ@mail.gmail.com>
Subject: Re: [PATCH v4] ceph: mark directory as non-complete complete after
 loading key
To:     Ilya Dryomov <idryomov@gmail.com>
Cc:     Xiubo Li <xiubli@redhat.com>, Venky Shankar <vshankar@redhat.com>,
        =?UTF-8?Q?Lu=C3=ADs_Henriques?= <lhenriques@suse.de>,
        Jeff Layton <jlayton@kernel.org>, ceph-devel@vger.kernel.org,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Tue, Nov 29, 2022 at 7:21 AM Ilya Dryomov <idryomov@gmail.com> wrote:
>
> On Tue, Nov 29, 2022 at 3:50 PM Xiubo Li <xiubli@redhat.com> wrote:
> >
> >
> > On 29/11/2022 22:32, Ilya Dryomov wrote:
> > > On Tue, Nov 29, 2022 at 3:15 PM Xiubo Li <xiubli@redhat.com> wrote:
> > >>
> > >> On 29/11/2022 18:39, Lu=C3=ADs Henriques wrote:
> > >>> When setting a directory's crypt context, ceph_dir_clear_complete()=
 needs to
> > >>> be called otherwise if it was complete before, any existing (old) d=
entry will
> > >>> still be valid.
> > >>>
> > >>> This patch adds a wrapper around __fscrypt_prepare_readdir() which =
will
> > >>> ensure a directory is marked as non-complete if key status changes.
> > >>>
> > >>> Signed-off-by: Lu=C3=ADs Henriques <lhenriques@suse.de>
> > >>> ---
> > >>> Hi Xiubo,
> > >>>
> > >>> Here's a rebase of this patch.  I did some testing but since this b=
ranch
> > >>> doesn't really have full fscrypt support, I couldn't even reproduce=
 the
> > >>> bug.  So, my testing was limited.
> > >> I'm planing not to update the wip-fscrypt branch any more, except th=
e IO
> > >> path related fixes, which may introduce potential bugs each time as =
before.
> > >>
> > >> Since the qa tests PR has finished and the tests have passed, so we =
are
> > >> planing to merge the first none IO part, around 27 patches. And then
> > >> pull the reset patches from wip-fscrypt branch.
> > > I'm not sure if merging metadata and I/O path patches separately
> > > makes sense.  What would a user do with just filename encryption?
> >
> > Hi Ilya,
> >
> > I think the IO ones should be followed soon.
> >
> > Currently the filename ones have been well testes. And the contents wil=
l
> > be by passed for now.
> >
> > Since this is just for Dev Preview feature IMO it should be okay (?)
>
> I don't think there is such a thing as a Dev Preview feature when it
> comes to the mainline kernel, particularly in the area of filesystems
> and storage.  It should be ready for users at least to some extent.  So
> my question stands: what would a user do with just filename encryption?

I think how this merges is up to you guys and the kernel practices.
Merging only the filename encryption is definitely of *limited*
utility, but I don't think it's totally pointless -- the data versus
metadata paths are different and you are protecting against somewhat
different vulnerabilities and threat models with them. For instance,
MDS logs dump filenames, but OSD logs do not dump object data. There's
some obvious utility there even if you basically trust your provider,
or run your own cluster but want to be more secure about sending logs
via ceph-post-file.
-Greg

>
> Thanks,
>
>                 Ilya
>