From: Tyler Hicks <tyhicks@canonical.com>
To: Simon Que <sque@chromium.org>
Cc: ecryptfs@vger.kernel.org, dustin.kirkland@gazzang.com, msb@chromium.org
Subject: Re: [PATCH v2] fs: ecryptfs: initialize payload_len in keystore.c
Date: Thu, 17 Jan 2013 13:39:58 -0800 [thread overview]
Message-ID: <20130117213957.GA13176@boyd> (raw)
In-Reply-To: <1358450300-23826-1-git-send-email-sque@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
On 2013-01-17 11:18:20, Simon Que wrote:
> This is meant to remove a compiler warning. It should not make any
> functional change.
>
> payload_len should be initialized when it is passed to
> write_tag_64_packet() as a pointer. If that call fails, this function
> should return early, and payload_len won't be used.
>
> Signed-off-by: Simon Que <sque@chromium.org>
Thanks for resubmitting. I've pushed it to the next branch at:
http://git.kernel.org/?p=linux/kernel/git/tyhicks/ecryptfs.git;a=summary
Tyler
> ---
> fs/ecryptfs/keystore.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/ecryptfs/keystore.c b/fs/ecryptfs/keystore.c
> index 2333203..6154cde 100644
> --- a/fs/ecryptfs/keystore.c
> +++ b/fs/ecryptfs/keystore.c
> @@ -1150,7 +1150,7 @@ decrypt_pki_encrypted_session_key(struct ecryptfs_auth_tok *auth_tok,
> struct ecryptfs_message *msg = NULL;
> char *auth_tok_sig;
> char *payload;
> - size_t payload_len;
> + size_t payload_len = 0;
> int rc;
>
> rc = ecryptfs_get_auth_tok_sig(&auth_tok_sig, auth_tok);
> --
> 1.7.8.6
>
> --
> To unsubscribe from this list: send the line "unsubscribe ecryptfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-01-17 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 19:18 [PATCH v2] fs: ecryptfs: initialize payload_len in keystore.c Simon Que
2013-01-17 21:39 ` Tyler Hicks [this message]
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=20130117213957.GA13176@boyd \
--to=tyhicks@canonical.com \
--cc=dustin.kirkland@gazzang.com \
--cc=ecryptfs@vger.kernel.org \
--cc=msb@chromium.org \
--cc=sque@chromium.org \
/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