From: Richard Weinberger <richard@nod.at>
To: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, jaegeuk@kernel.org,
Theodore Ts'o <tytso@mit.edu>,
ebiggers@google.com, david@sigma-star.at
Subject: Re: [PATCH] fscrypt: properly declare on-stack completion
Date: Wed, 1 Feb 2017 21:34:09 +0100 [thread overview]
Message-ID: <225430ef-9f08-bde3-4ad3-78d41b0464d2@nod.at> (raw)
In-Reply-To: <20170201203209.17710-1-richard@nod.at>
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
next prev parent reply other threads:[~2017-02-01 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 20:32 [PATCH] fscrypt: properly declare on-stack completion Richard Weinberger
2017-02-01 20:34 ` Richard Weinberger [this message]
2017-02-07 4:21 ` Theodore Ts'o
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=225430ef-9f08-bde3-4ad3-78d41b0464d2@nod.at \
--to=richard@nod.at \
--cc=david@sigma-star.at \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).