public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trevor Highland <thighlan@gmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	ecryptfs-devel@lists.sourceforge.net, mhalcrow@us.ibm.com
Subject: [PATCH] eCryptfs: Load each file decryption key only once
Date: Tue, 18 Dec 2007 00:11:37 -0600	[thread overview]
Message-ID: <1197958297.10903.10.camel@buster2> (raw)

[-- Attachment #1: Type: text/plain, Size: 91 bytes --]

There is no need to set the decryption key every time eCryptfs decrypts
an extent.

Trevor

[-- Attachment #2: 0001-eCryptfs-Load-each-file-decryption-key-only-once.patch --]
[-- Type: application/mbox, Size: 1511 bytes --]

             reply	other threads:[~2007-12-18  6:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18  6:11 Trevor Highland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-12-19  2:37 [PATCH] eCryptfs: Load each file decryption key only once Trevor Highland
2007-12-22  2:05 Trevor Highland
2008-01-08 21:17 ` Michael Halcrow
2008-01-08 22:47   ` Andrew Morton

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=1197958297.10903.10.camel@buster2 \
    --to=thighlan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ecryptfs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhalcrow@us.ibm.com \
    /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