fscrypt: properly declare on-stack completion
authorRichard Weinberger <richard@nod.at>
Wed, 1 Feb 2017 20:32:09 +0000 (21:32 +0100)
committerTheodore Ts'o <tytso@mit.edu>
Tue, 7 Feb 2017 04:45:28 +0000 (23:45 -0500)
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>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
fs/crypto/fscrypt_private.h

index e8a229e1d45de238d494f7e4a7b61a50fc00a033..fdbb8af32eafdb6bae492658d376abf15f8a3d69 100644 (file)
@@ -86,7 +86,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 */