lkml.org 
[lkml]   [2017]   [Feb]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] fscrypt: properly declare on-stack completion
From
Date
Am 01.02.2017 um 21:32 schrieb Richard Weinberger:
> When a completion is declared on-stack we have to use
> COMPLETION_INITIALIZER_ONSTACK().
>
> Fixes: 0b81d07790726 ("fs crypto: move per-file encryption from f2fs
> tree to fs/crypto")
> Signed-off-by: Richard Weinberger <richard@nod.at>
>
> ---
> fs/crypto/fscrypt_private.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/crypto/fscrypt_private.h b/fs/crypto/fscrypt_private.h
> index aeab032d7d35..a0494a164f97 100644
> --- a/fs/crypto/fscrypt_private.h
> +++ b/fs/crypto/fscrypt_private.h
> @@ -81,7 +81,7 @@ struct fscrypt_completion_result {
>
> #define DECLARE_FS_COMPLETION_RESULT(ecr) \
> struct fscrypt_completion_result ecr = { \
> - COMPLETION_INITIALIZER((ecr).completion), 0 }
> + COMPLETION_INITIALIZER_ONSTACK((ecr).completion), 0 }
>
>
> /* crypto.c */
>

Replying with Ted's corrected mail address... ;-\

Thanks,
//richard

\
 
 \ /
  Last update: 2017-02-01 21:35    [W:0.030 / U:2.992 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site