linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tyler Hicks <tyhicks@linux.vnet.ibm.com>
To: Roberto Sassu <roberto.sassu@polito.it>
Cc: kirkland@canonical.com, dhowells@redhat.com, jmorris@namei.org,
	linux-fsdevel@vger.kernel.org, keyrings@linux-nfs.org,
	linux-kernel@vger.kernel.org, ecryptfs-devel@lists.launchpad.net
Subject: Re: [PATCH 2/5] eCryptfs: modified size of keysig in the ecryptfs_key_sig structure
Date: Fri, 18 Mar 2011 10:52:10 -0500	[thread overview]
Message-ID: <20110318155209.GC22193@boyd.l.tihix.com> (raw)
In-Reply-To: <1300362538-11502-3-git-send-email-roberto.sassu@polito.it>

On Thu Mar 17, 2011 at 12:48:51PM +0100, Roberto Sassu <roberto.sassu@polito.it> wrote:
> The size of the 'keysig' array is incremented of one byte in order to make
> room for the NULL character.

Hello Roberto - I'm assuming that this change is because you want to
print the keysig in patch 3/5. I don't see where we are currently trying
to print the keysig, so I'll wait until you resubmit this patch set to
merge this one.

Along with what a patch does, please try to explain why it is useful in
the commit message.

Tyler

> 
> Signed-off-by: Roberto Sassu <roberto.sassu@polito.it>
> ---
>  fs/ecryptfs/ecryptfs_kernel.h |    2 +-
>  fs/ecryptfs/keystore.c        |    1 +
>  2 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/ecryptfs/ecryptfs_kernel.h b/fs/ecryptfs/ecryptfs_kernel.h
> index e007534..8282031 100644
> --- a/fs/ecryptfs/ecryptfs_kernel.h
> +++ b/fs/ecryptfs/ecryptfs_kernel.h
> @@ -233,7 +233,7 @@ ecryptfs_get_key_payload_data(struct key *key)
> 
>  struct ecryptfs_key_sig {
>  	struct list_head crypt_stat_list;
> -	char keysig[ECRYPTFS_SIG_SIZE_HEX];
> +	char keysig[ECRYPTFS_SIG_SIZE_HEX + 1];
>  };
> 
>  struct ecryptfs_filename {
> diff --git a/fs/ecryptfs/keystore.c b/fs/ecryptfs/keystore.c
> index 4feb78c..36b68a6 100644
> --- a/fs/ecryptfs/keystore.c
> +++ b/fs/ecryptfs/keystore.c
> @@ -2425,6 +2425,7 @@ int ecryptfs_add_keysig(struct ecryptfs_crypt_stat *crypt_stat, char *sig)
>  		return -ENOMEM;
>  	}
>  	memcpy(new_key_sig->keysig, sig, ECRYPTFS_SIG_SIZE_HEX);
> +	new_key_sig->keysig[ECRYPTFS_SIG_SIZE_HEX] = '\0';
>  	/* Caller must hold keysig_list_mutex */
>  	list_add(&new_key_sig->crypt_stat_list, &crypt_stat->keysig_list);
> 
> -- 
> 1.7.4
> 

  reply	other threads:[~2011-03-18 15:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 11:48 [PATCH 0/5] eCryptfs key locking patches Roberto Sassu
2011-03-17 11:48 ` [PATCH 1/5] eCryptfs: ecryptfs_keyring_auth_tok_for_sig() bug fix Roberto Sassu
2011-03-18 16:02   ` Tyler Hicks
2011-03-17 11:48 ` [PATCH 2/5] eCryptfs: modified size of keysig in the ecryptfs_key_sig structure Roberto Sassu
2011-03-18 15:52   ` Tyler Hicks [this message]
2011-03-17 11:48 ` [PATCH 3/5] eCryptfs: verify authentication tokens before their use Roberto Sassu
2011-03-18  3:05   ` Tyler Hicks
2011-03-18  9:21     ` Roberto Sassu
2011-03-17 11:48 ` [PATCH 4/5] eCryptfs: move ecryptfs_find_auth_tok_for_sig() call before mutex_lock Roberto Sassu
2011-03-18 15:30   ` Tyler Hicks
2011-03-18 15:44     ` Roberto Sassu
2011-03-17 11:48 ` [PATCH 5/5] eCryptfs: write lock requested keys 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=20110318155209.GC22193@boyd.l.tihix.com \
    --to=tyhicks@linux.vnet.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=ecryptfs-devel@lists.launchpad.net \
    --cc=jmorris@namei.org \
    --cc=keyrings@linux-nfs.org \
    --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).