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;
Subject: Re: [PATCH v4] ceph: mark directory as non-complete complete after
 loading key
To:     Ilya Dryomov <idryomov@gmail.com>
Cc:     Venky Shankar <vshankar@redhat.com>,
        Gregory Farnum <gfarnum@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
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>
From:   Xiubo Li <xiubli@redhat.com>
Message-ID: <fcbba3e5-9187-c174-a783-ddf08925b3da@redhat.com>
Date:   Wed, 30 Nov 2022 06:37:26 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <CAOi1vP_H8jE4ZU4a4srhQev3odECgZD1LyxA8dv+Fk-bVDvoyQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Precedence: bulk


On 29/11/2022 23:21, Ilya Dryomov 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ís 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) dentry 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ís Henriques <lhenriques@suse.de>
>>>>> ---
>>>>> Hi Xiubo,
>>>>>
>>>>> Here's a rebase of this patch.  I did some testing but since this branch
>>>>> 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 the 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 will
>> 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?

Before why split these patches was that, the content patches will change 
a lot and this may will stay in the testing branch for months. This will 
make it hard to test and rebase the non-encrypt patches based on encrypt 
ones when trying to pick and merge them.

The filename ones are simple and won't have the issue.

No worry, I can try to pick the content patches from wip-fscrypt branch 
soon. But before that please help check the existing non-encypt patches 
in the testing branch are okay and won't do big change later, which will 
always make me to rebase the content patches again and again and may 
involve many changes and potential bugs.

Thanks!

- Xiubo


> Thanks,
>
>                  Ilya
>