From: Nigel Cunningham <nigel@suspend2.net>
To: linux-kernel@vger.kernel.org
Subject: [Suspend2][ 06/12] [Suspend2] Decrypt a page in the image.
Date: Tue, 27 Jun 2006 14:38:23 +1000 [thread overview]
Message-ID: <20060627043822.14437.47583.stgit@nigel.suspend2.net> (raw)
In-Reply-To: <20060627043803.14437.68085.stgit@nigel.suspend2.net>
Add support for decrypting a page being read from the storage.
Signed-off-by: Nigel Cunningham <nigel@suspend2.net>
kernel/power/encryption.c | 41 +++++++++++++++++++++++++++++++++++++++++
1 files changed, 41 insertions(+), 0 deletions(-)
diff --git a/kernel/power/encryption.c b/kernel/power/encryption.c
index 9b7dd93..cd26e84 100644
--- a/kernel/power/encryption.c
+++ b/kernel/power/encryption.c
@@ -238,3 +238,44 @@ static int suspend_encrypt_rw_init(int r
return 0;
}
+/* suspend_encrypt_read_chunk()
+ *
+ * Description: Retrieve data from later modules and deencrypt it until the
+ * input buffer is filled.
+ * Arguments: Buffer_start: Pointer to a buffer of size PAGE_SIZE.
+ * Sync: Whether the previous module (or core) wants its
+ * data synchronously.
+ * Returns: Zero if successful. Error condition from me or from downstream
+ * on failure.
+ */
+static int suspend_encrypt_read_chunk(struct page *buffer_page, int sync)
+{
+ int ret;
+ char *buffer_start;
+
+ if (!suspend_encryptor_transform)
+ return next_driver->read_chunk(buffer_page, sync);
+
+ /*
+ * All our reads must be synchronous - we can't deencrypt
+ * data that hasn't been read yet.
+ */
+
+ if ((ret = next_driver->read_chunk(
+ virt_to_page(page_buffer), SUSPEND_SYNC)) < 0) {
+ printk("Failed to read an encrypted block.\n");
+ return ret;
+ }
+
+ ret = crypto_cipher_decrypt(suspend_encryptor_transform,
+ suspend_crypt_sg, suspend_crypt_sg, PAGE_SIZE);
+
+ if (ret)
+ printk("Decrypt function returned %d.\n", ret);
+
+ buffer_start = kmap(buffer_page);
+ memcpy(buffer_start, page_buffer, PAGE_SIZE);
+ kunmap(buffer_page);
+ return ret;
+}
+
--
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 ` [Suspend2][ 02/12] [Suspend2] Encryption buffer allocation Nigel Cunningham
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 ` Nigel Cunningham [this message]
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=20060627043822.14437.47583.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®