linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Halcrow <lkml@halcrow.us>
To: Phillip Hellewell <phillip@hellewell.homeip.net>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	mhalcrow@us.ibm.com, mcthomps@us.ibm.com, yoder1@us.ibm.com
Subject: Re: [PATCH 10/12: eCryptfs] Mmap operations
Date: Wed, 2 Nov 2005 23:32:58 -0600	[thread overview]
Message-ID: <20051103053258.GA32733@halcrow.us> (raw)
In-Reply-To: <20051103035530.GJ3005@sshock.rn.byu.edu>

On Wed, Nov 02, 2005 at 08:55:30PM -0700, Phillip Hellewell wrote:
> +static int ecryptfs_writepage(struct page *page, struct writeback_control *wbc)
> +{
> ...
> +	ecryptfs_printk(1, KERN_NOTICE, "Copying page\n");
> +	memcpy(lower_kaddr, kaddr, crypt_stats->extent_size);

Note that this serves only to reduce the complexity of the execution
path while we try to pin down the kernel oops that shows up on certain
sets of concurrent gcc jobs. When actually encrypting, we are doing
extra page reads and writes with the underlying file to juggle the
initialization vectors. This part will, of course, need to be replaced
with the same crypto operations being done in ecryptfs_commit_write()
in order to encrypt the data on its way out via ecryptfs_writepage().
I will test the patch to do this and offer it as a follow-up once I am
satisfied that it does not regress any of our testcases; this patch
will also reduce the size of the ecryptfs_commit_write() function to
be closer to what it should be.

Thanks,
Mike

  reply	other threads:[~2005-11-03  5:36 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03  3:32 [PATCH 0/12: eCryptfs] eCryptfs version 0.1 Phillip Hellewell
2005-11-03  3:42 ` [PATCH 1/12: eCryptfs] Makefile and Kconfig Phillip Hellewell
2005-11-03 15:21   ` Michael Thompson
2005-11-03 23:05     ` Greg KH
2005-11-04 16:09       ` Michael Thompson
2005-11-04 16:22         ` Anton Altaparmakov
2005-11-04 16:28           ` Michael Thompson
2005-11-04 16:35         ` Greg KH
2005-11-04 17:07           ` Michael Thompson
2005-11-03  3:43 ` [PATCH 2/12: eCryptfs] Documentation Phillip Hellewell
2005-11-03  3:43 ` [PATCH 3/12: eCryptfs] Makefile Phillip Hellewell
2005-11-03  3:49 ` [PATCH 4/12: eCryptfs] Main module functions Phillip Hellewell
2005-11-03  6:02   ` Greg KH
2005-11-03 15:09     ` Michael Thompson
2005-11-03 15:47       ` Alexey Dobriyan
2005-11-03 15:40         ` Michael Thompson
2005-11-03 21:34     ` Michael Thompson
2005-11-04 23:28     ` [PATCH: eCryptfs] Remove debug wrappers Michael Halcrow
2005-11-03  3:50 ` [PATCH 5/12: eCryptfs] Header declarations Phillip Hellewell
2005-11-03 23:37   ` James Morris
2005-11-03  3:51 ` [PATCH 6/12: eCryptfs] Superblock operations Phillip Hellewell
2005-11-03 23:47   ` James Morris
2005-11-03  3:52 ` [PATCH 7/12: eCryptfs] File operations Phillip Hellewell
2005-11-03 23:49   ` James Morris
2005-11-03  3:53 ` [PATCH 8/12: eCryptfs] Dentry operations Phillip Hellewell
2005-11-03  3:54 ` [PATCH 9/12: eCryptfs] Inode operations Phillip Hellewell
2005-11-03 23:51   ` James Morris
2005-11-04  0:24     ` Andreas Schwab
2005-11-04  6:29       ` James Morris
2005-11-03  3:55 ` [PATCH 10/12: eCryptfs] Mmap operations Phillip Hellewell
2005-11-03  5:32   ` Michael Halcrow [this message]
2005-11-07 20:39     ` [PATCH: eCryptfs] Encrypt on writepage() Michael Halcrow
2005-11-03  3:56 ` [PATCH 11/12: eCryptfs] Keystore Phillip Hellewell
2005-11-03 23:59   ` James Morris
2005-11-04  0:08     ` Michael Halcrow
2005-11-04 17:52   ` Timothy R. Chavez
2005-11-03  3:56 ` [PATCH 12/12: eCryptfs] Crypto functions Phillip Hellewell
2005-11-03 22:06   ` Dave Kleikamp
2005-11-03 22:25     ` Michael Thompson
2005-11-03 22:30       ` Dave Kleikamp
2005-11-04  0:08   ` James Morris
2005-11-04  0:14     ` Michael Halcrow
  -- strict thread matches above, loose matches on Subject: below --
2005-11-19  4:11 [PATCH 0/12: eCryptfs] eCryptfs version 0.1 Phillip Hellewell
2005-11-19  4:22 ` [PATCH 10/12: eCryptfs] Mmap operations Phillip Hellewell

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=20051103053258.GA32733@halcrow.us \
    --to=lkml@halcrow.us \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcthomps@us.ibm.com \
    --cc=mhalcrow@us.ibm.com \
    --cc=phillip@hellewell.homeip.net \
    --cc=yoder1@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;
as well as URLs for NNTP newsgroup(s).