All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Xiubo Li <xiubli@redhat.com>,
	ceph-devel@vger.kernel.org, idryomov@gmail.com
Cc: vshankar@redhat.com, linux-kernel@vger.kernel.org,
	Eric Biggers <ebiggers@kernel.org>
Subject: Re: [PATCH] ceph: fix up test_dummy_encryption handling for new mount API
Date: Wed, 13 Jul 2022 14:56:15 -0400	[thread overview]
Message-ID: <5edd2424465dc97e15d3e4635c7011e5c789cef1.camel@kernel.org> (raw)
In-Reply-To: <b82c4486-42ea-cdd1-8204-6dcc95836f72@redhat.com>

On Wed, 2022-07-13 at 20:55 +0800, Xiubo Li wrote:
> Hi Jeff,
> 
> I am rebasing the 'wip-fscrypt' branch to the 'testing', and there is 
> one commit conflicts:
> 
> commit 81faddddbef409bcaa1aa3d89e59606cde94dab7
> Author: Jeff Layton <jlayton@kernel.org>
> Date:   Wed Dec 1 09:21:39 2021 -0500
> 
>      ceph: add infrastructure for file encryption and decryption
> 
>      ...and allow test_dummy_encryption to bypass content encryption
>      if mounted with test_dummy_encryption=clear.
> 
>      Reviewed-by: Xiubo Li <xiubli@redhat.com>
>      Signed-off-by: Jeff Layton <jlayton@kernel.org>
> 
> And the conflicts are:
> 
> [xiubli@fedora ]$ cat fs/ceph/super.h.rej
> --- fs/ceph/super.h
> +++ fs/ceph/super.h
> @@ -45,6 +45,7 @@
>   #define CEPH_MOUNT_OPT_NOPAGECACHE     (1<<16) /* bypass pagecache 
> altogether */
>   #define CEPH_MOUNT_OPT_SPARSEREAD      (1<<17) /* always do sparse 
> reads */
>   #define CEPH_MOUNT_OPT_TEST_DUMMY_ENC  (1<<18) /* enable dummy 
> encryption (for testing) */
> +#define CEPH_MOUNT_OPT_DUMMY_ENC_CLEAR (1<<19) /* don't actually 
> encrypt content */
> 
>   #define CEPH_MOUNT_OPT_DEFAULT            \
>       (CEPH_MOUNT_OPT_DCACHE |        \
> 
> [xiubli@fedora ]$ cat fs/ceph/super.c.rej
> --- fs/ceph/super.c
> +++ fs/ceph/super.c
> @@ -1098,6 +1098,14 @@ static int ceph_set_test_dummy_encryption(struct 
> super_block *sb, struct fs_cont
>               return -EEXIST;
>           }
> 
> +        /* HACK: allow for cleartext "encryption" in files for testing */
> +        if (fsc->mount_options->test_dummy_encryption &&
> + !strcmp(fsc->mount_options->test_dummy_encryption, "clear")) {
> +            fsopt->flags |= CEPH_MOUNT_OPT_DUMMY_ENC_CLEAR;
> + kfree(fsc->mount_options->test_dummy_encryption);
> +            fsc->mount_options->test_dummy_encryption = NULL;
> +        }
> +
>           err = fscrypt_set_test_dummy_encryption(sb,
> fsc->mount_options->test_dummy_encryption,
>                               &fsc->dummy_enc_policy);
> 
> And I have pushed the tmp patches to 
> https://github.com/lxbsz/ceph-client/commits/lxb-wip-fscrypt3.
> 
> Please take a look is that okay ?
> 
> Thanks
> 
> -- Xiubo
> 
> 

The result looks good to me. Thanks for fixing this up.

-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2022-07-13 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13  8:56 [PATCH] ceph: fix up test_dummy_encryption handling for new mount API xiubli
2022-07-13 10:42 ` Jeff Layton
2022-07-13 10:49   ` Xiubo Li
2022-07-13 12:55   ` Xiubo Li
2022-07-13 18:56     ` Jeff Layton [this message]
2022-07-14  0:41       ` Xiubo Li

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=5edd2424465dc97e15d3e4635c7011e5c789cef1.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=idryomov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vshankar@redhat.com \
    --cc=xiubli@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.