public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Xiubo Li <xiubli@redhat.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v3] encrypt: add ceph support
Date: Tue, 1 Nov 2022 09:51:46 +0800	[thread overview]
Message-ID: <79584e5e-fd3d-9870-e421-289958dc5f8e@redhat.com> (raw)
In-Reply-To: <20221031150404.etbrz45c7bkgcgdb@zlang-mailbox>


On 31/10/2022 23:04, Zorro Lang wrote:
> On Mon, Oct 31, 2022 at 04:38:19PM +0800, xiubli@redhat.com wrote:
>> From: Xiubo Li <xiubli@redhat.com>
>>
>> This will enable ceph could run the fscrypt test cases, but not all.
>> Some of them will be skipped because of not supporting features.
>>
>> Here will just skip ceph in _scratch_mkfs_encrypted() and in
>> _require_scratch_encryption() it will try to check "set_encpolicy"
>> to make sure whether kernel ceph support the encryption or not.
>>
>> Reviewed-by: Zorro Lang <zlang@redhat.com>
>> Signed-off-by: Xiubo Li <xiubli@redhat.com>
>> ---
>>
>> V3:
>> - Add more commit comments.
> V2 patch has been merged and pushed.

Ah Okay.

Sorry, I pulled it and didn't see that yesterday.

I may missed that.

Thanks Zorro!


> Thanks,
> Zorro
>
>>
>>   common/encrypt | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/common/encrypt b/common/encrypt
>> index 45ce0954..1a77e23b 100644
>> --- a/common/encrypt
>> +++ b/common/encrypt
>> @@ -153,6 +153,9 @@ _scratch_mkfs_encrypted()
>>   		# erase the UBI volume; reformated automatically on next mount
>>   		$UBIUPDATEVOL_PROG ${SCRATCH_DEV} -t
>>   		;;
>> +	ceph)
>> +		_scratch_cleanup_files
>> +		;;
>>   	*)
>>   		_notrun "No encryption support for $FSTYP"
>>   		;;
>> -- 
>> 2.31.1
>>


      reply	other threads:[~2022-11-01  1:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  8:38 [PATCH v3] encrypt: add ceph support xiubli
2022-10-31 15:04 ` Zorro Lang
2022-11-01  1:51   ` 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=79584e5e-fd3d-9870-e421-289958dc5f8e@redhat.com \
    --to=xiubli@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=zlang@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