From: Xiubo Li <xiubli@redhat.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: ceph-devel@vger.kernel.org, idryomov@gmail.com,
jlayton@kernel.org, vshankar@redhat.com, mchangir@redhat.com
Subject: Re: [PATCH] ceph: always set the initial i_blkbits to CEPH_FSCRYPT_BLOCK_SHIFT
Date: Thu, 25 Jan 2024 10:01:20 +0800 [thread overview]
Message-ID: <cedd83f2-de68-4733-92bb-5514440b40a2@redhat.com> (raw)
In-Reply-To: <20240125015305.GG1088@sol.localdomain>
On 1/25/24 09:53, Eric Biggers wrote:
> On Thu, Jan 18, 2024 at 04:04:04PM +0800, xiubli@redhat.com wrote:
>> From: Xiubo Li <xiubli@redhat.com>
>>
>> The fscrypt code will use i_blkbits to setup the 'ci_data_unit_bits'
>> when allocating the new inode, but ceph will initiate i_blkbits
>> ater when filling the inode, which is too late. Since the
>> 'ci_data_unit_bits' will only be used by the fscrypt framework so
>> initiating i_blkbits with CEPH_FSCRYPT_BLOCK_SHIFT is safe.
>>
>> Fixes: commit 5b1188847180 ("fscrypt: support crypto data unit size
>> less than filesystem block size")
> The Fixes line should be one line, and the word "commit" should not be there
Sure, I will fix it.
>> URL: https://tracker.ceph.com/issues/64035
>> Signed-off-by: Xiubo Li <xiubli@redhat.com>
>> ---
>> fs/ceph/inode.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/fs/ceph/inode.c b/fs/ceph/inode.c
>> index 62af452cdba4..d96d97b31f68 100644
>> --- a/fs/ceph/inode.c
>> +++ b/fs/ceph/inode.c
>> @@ -79,6 +79,8 @@ struct inode *ceph_new_inode(struct inode *dir, struct dentry *dentry,
>> if (!inode)
>> return ERR_PTR(-ENOMEM);
>>
>> + inode->i_blkbits = CEPH_FSCRYPT_BLOCK_SHIFT;
>> +
>> if (!S_ISLNK(*mode)) {
>> err = ceph_pre_init_acls(dir, mode, as_ctx);
>> if (err < 0)
> Looks good, you can add:
>
> Reviewed-by: Eric Biggers <ebiggers@google.com>
>
> Sorry for the trouble; I need to start running xfstests on CephFS!
Thanks Eric, no worry, this will only be seen when the
'test_dummy_encryption' is enabled.
> In the future please also Cc the fscrypt mailing list on things like this.
Sure, I meant to Cc you but I think I forgot that. Sorry.
> Maybe you'd like to also send a patch that updates the comment for
> fscrypt_prepare_new_inode() to clarify that i_blkbits needs to be set first?
Will fix it.
Thanks Eric.
- Xiubo
> - Eric
>
prev parent reply other threads:[~2024-01-25 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 8:04 [PATCH] ceph: always set the initial i_blkbits to CEPH_FSCRYPT_BLOCK_SHIFT xiubli
2024-01-25 1:53 ` Eric Biggers
2024-01-25 2:01 ` Xiubo Li [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cedd83f2-de68-4733-92bb-5514440b40a2@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ebiggers@kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=mchangir@redhat.com \
--cc=vshankar@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox