[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6901.1296041316@redhat.com>
Date: Wed, 26 Jan 2011 11:28:36 +0000
From: David Howells <dhowells@...hat.com>
To: Roberto Sassu <roberto.sassu@...ito.it>
Cc: dhowells@...hat.com, linux-security-module@...r.kernel.org,
keyrings@...ux-nfs.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, jmorris@...ei.org,
zohar@...ux.vnet.ibm.com, safford@...son.ibm.com,
ramunno@...ito.it, tyhicks@...ux.vnet.ibm.com,
kirkland@...onical.com
Subject: Re: [RFC][PATCH v3 6/6] eCryptfs: added support for the encrypted key type
Roberto Sassu <roberto.sassu@...ito.it> wrote:
> (*auth_tok_key) = request_key(&key_type_user, sig, NULL);
> if (!(*auth_tok_key) || IS_ERR(*auth_tok_key)) {
> - printk(KERN_ERR "Could not find key with description: [%s]\n",
> - sig);
> - rc = process_request_key_err(PTR_ERR(*auth_tok_key));
> - goto out;
> + (*auth_tok_key) = ecryptfs_get_encrypted_key(sig);
> + if (!(*auth_tok_key) || IS_ERR(*auth_tok_key)) {
> + printk(KERN_ERR "Could not find key with description: [%s]\n",
> + sig);
> + rc = process_request_key_err(PTR_ERR(*auth_tok_key));
> + goto out;
> + }
> }
> (*auth_tok) = ecryptfs_get_key_payload_data(*auth_tok_key);
> if (ecryptfs_verify_version((*auth_tok)->version)) {
You need some locking here, even if it's only use of the RCU read lock.
Encrypted-type keys have an update method and so may change under you.
David
---
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists