From: Tyler Hicks <tyhicks@linux.vnet.ibm.com>
To: Roberto Sassu <roberto.sassu@polito.it>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
kirkland@canonical.com, ecryptfs-devel@lists.launchpad.net,
hilld@binarystorm.net
Subject: Re: [PATCH] eCryptfs: fix compile error
Date: Fri, 29 Jul 2011 12:09:32 -0500 [thread overview]
Message-ID: <20110729170932.GC29604@boyd.l.tihix.com> (raw)
In-Reply-To: <1311958266-3724-1-git-send-email-roberto.sassu@polito.it>
On Fri Jul 29, 2011 at 06:51:04PM +0200, Roberto Sassu <roberto.sassu@polito.it> wrote:
> This patch fixes the compile error reported at the address:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=40292
>
> The problem arises when compiling eCryptfs as built-in and the 'encrypted'
> key type as a module. The patch enables the 'encrypted' key type support
> for eCryptfs only when both components are compiled as built-in, both as
> modules or eCryptfs as a module and the 'encrypted' key type as built-in.
>
> Signed-off-by: Roberto Sassu <roberto.sassu@polito.it>
> Reported-by: David Hill <hilld@binarystorm.net>
> ---
> fs/ecryptfs/ecryptfs_kernel.h | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/fs/ecryptfs/ecryptfs_kernel.h b/fs/ecryptfs/ecryptfs_kernel.h
> index b36c557..a2da660 100644
> --- a/fs/ecryptfs/ecryptfs_kernel.h
> +++ b/fs/ecryptfs/ecryptfs_kernel.h
> @@ -79,7 +79,9 @@ struct ecryptfs_page_crypt_context {
> } param;
> };
>
> -#if defined(CONFIG_ENCRYPTED_KEYS) || defined(CONFIG_ENCRYPTED_KEYS_MODULE)
> +#if (defined(CONFIG_ECRYPT_FS) && defined(CONFIG_ENCRYPTED_KEYS)) || \
> + (defined(CONFIG_ECRYPT_FS_MODULE) && \
> + (defined(CONFIG_ENCRYPTED_KEYS) || defined(CONFIG_ENCRYPTED_KEYS_MODULE)))
Thanks for the patch, Roberto.
Shouldn't this be handled in the Kconfig? It seems like it would be
better to force the encrypted key type to be built-in if eCryptfs is
configured to be built-in.
With this patch, a user could have CONFIG_ENCRYPTED_KEYS=m and
CONFIG_ECRYPT_FS=y, but still hit potentially confusing error conditions
when trying to use encrypted key support with eCryptfs.
Tyler
> static inline struct ecryptfs_auth_tok *
> ecryptfs_get_encrypted_key_payload_data(struct key *key)
> {
> --
> 1.7.6
>
next prev parent reply other threads:[~2011-07-29 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 16:51 [PATCH] eCryptfs: fix compile error Roberto Sassu
2011-07-29 17:09 ` Tyler Hicks [this message]
2011-08-01 11:31 ` Roberto Sassu
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=20110729170932.GC29604@boyd.l.tihix.com \
--to=tyhicks@linux.vnet.ibm.com \
--cc=ecryptfs-devel@lists.launchpad.net \
--cc=hilld@binarystorm.net \
--cc=kirkland@canonical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roberto.sassu@polito.it \
/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;
as well as URLs for NNTP newsgroup(s).