From: Nigel Cunningham <nigel@suspend2.net>
To: linux-kernel@vger.kernel.org
Subject: [Suspend2][ 02/12] [Suspend2] Encryption buffer allocation.
Date: Tue, 27 Jun 2006 14:38:10 +1000 [thread overview]
Message-ID: <20060627043809.14437.61345.stgit@nigel.suspend2.net> (raw)
In-Reply-To: <20060627043803.14437.68085.stgit@nigel.suspend2.net>
Add support for allocating and freeing buffers used for encryption.
Signed-off-by: Nigel Cunningham <nigel@suspend2.net>
kernel/power/encryption.c | 51 +++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 51 insertions(+), 0 deletions(-)
diff --git a/kernel/power/encryption.c b/kernel/power/encryption.c
index a90d3ca..45d325d 100644
--- a/kernel/power/encryption.c
+++ b/kernel/power/encryption.c
@@ -45,3 +45,54 @@ static unsigned int bufofs;
static struct scatterlist suspend_crypt_sg[PAGE_SIZE/8];
+/* ---- Local buffer management ---- */
+
+/* allocate_local_buffer
+ *
+ * Description: Allocates a page of memory for buffering output.
+ * Returns: Int: Zero if successful, -ENONEM otherwise.
+ */
+static int allocate_local_buffer(void)
+{
+ if (!page_buffer) {
+ int i, remainder;
+
+ page_buffer = (char *) get_zeroed_page(GFP_ATOMIC);
+
+ if (!page_buffer) {
+ printk(KERN_ERR
+ "Failed to allocate the page buffer for "
+ "suspend2 encryption driver.\n");
+ return -ENOMEM;
+ }
+
+ for (i=0; i < (PAGE_SIZE / suspend_key_len); i++) {
+ suspend_crypt_sg[i].page = virt_to_page(page_buffer);
+ suspend_crypt_sg[i].offset = suspend_key_len * i;
+ suspend_crypt_sg[i].length = suspend_key_len;
+ }
+
+ remainder = PAGE_SIZE % suspend_key_len;
+
+ if (remainder) {
+ suspend_crypt_sg[i].page = virt_to_page(page_buffer);
+ suspend_crypt_sg[i].offset = suspend_key_len * i;
+ suspend_crypt_sg[i].length = remainder;
+ }
+ }
+
+ return 0;
+}
+
+/* free_local_buffer
+ *
+ * Description: Frees memory allocated for buffering output.
+ */
+static void free_local_buffer(void)
+{
+ if (page_buffer)
+ free_page((unsigned long) page_buffer);
+
+ page_buffer = NULL;
+}
+
--
Nigel Cunningham nigel at suspend2 dot net
next prev parent reply other threads:[~2006-06-27 4:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 4:38 [Suspend2][ 00/12] Encryption support Nigel Cunningham
2006-06-27 4:38 ` [Suspend2][ 01/12] [Suspend2] Encryption support header Nigel Cunningham
2006-06-27 4:38 ` Nigel Cunningham [this message]
2006-06-27 4:38 ` [Suspend2][ 03/12] [Suspend2] Encryption rw init & cleanup routines Nigel Cunningham
2006-06-27 4:38 ` [Suspend2][ 04/12] [Suspend2] Encrypt a page being written Nigel Cunningham
2006-06-27 4:38 ` [Suspend2][ 05/12] [Suspend2] Prepare to encrypt or decrypt a stream of pages Nigel Cunningham
2006-06-27 4:38 ` [Suspend2][ 06/12] [Suspend2] Decrypt a page in the image Nigel Cunningham
2006-06-27 4:38 ` [Suspend2][ 07/12] [Suspend2] Encryption debug stats Nigel Cunningham
2006-06-27 4:38 ` [Suspend2][ 08/12] [Suspend2] Encryption resources needed Nigel Cunningham
2006-06-27 4:38 ` [Suspend2][ 09/12] [Suspend2] Encryption configuration serialisation Nigel Cunningham
2006-06-27 4:38 ` [Suspend2][ 10/12] [Suspend2] Encryption proc entries Nigel Cunningham
2006-06-27 4:38 ` [Suspend2][ 11/12] [Suspend2] Encryption module accessors structure Nigel Cunningham
2006-06-27 4:38 ` [Suspend2][ 12/12] [Suspend2] Load and unload routines Nigel Cunningham
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=20060627043809.14437.61345.stgit@nigel.suspend2.net \
--to=nigel@suspend2.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®