All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tyler Hicks <tyhicks@canonical.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, ecryptfs@vger.kernel.org
Subject: [GIT PULL] eCryptfs fixes for 3.6-rc1
Date: Wed, 1 Aug 2012 23:00:47 -0700	[thread overview]
Message-ID: <20120802060047.GA24033@boyd> (raw)

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

Hi Linus,

The following changes since commit bd0a521e88aa7a06ae7aabaed7ae196ed4ad867a:

  Linux 3.5-rc6 (2012-07-07 17:23:56 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git tags/ecryptfs-3.6-rc1-fixes

for you to fetch changes up to 5f5b331d5c21228a6519dcb793fc1629646c51a6:

  eCryptfs: check for eCryptfs cipher support at mount (2012-07-13 17:20:34 -0700)

----------------------------------------------------------------
- Fixes a bug when the lower filesystem mount options include 'acl', but the
  eCryptfs mount options do not
- Cleanups in the messaging code
- Better handling of empty files in the lower filesystem to improve usability.
  Failed file creations are now cleaned up and empty lower files are converted
  into eCryptfs during open().
- The write-through cache changes are being reverted due to bugs that are not
  easy to fix. Stability outweighs the performance enhancements here.
- Improvement to the mount code to catch unsupported ciphers specified in the
  mount options

----------------------------------------------------------------
Tim Sally (1):
      eCryptfs: check for eCryptfs cipher support at mount

Tyler Hicks (6):
      eCryptfs: Copy up POSIX ACL and read-only flags from lower mount
      eCryptfs: Remove unused messaging declarations and function
      eCryptfs: Make all miscdev functions use daemon ptr in file private_data
      eCryptfs: Unlink lower inode when ecryptfs_create() fails
      eCryptfs: Initialize empty lower files when opening them
      eCryptfs: Revert to a writethrough cache model

 fs/ecryptfs/ecryptfs_kernel.h |   24 +++-----
 fs/ecryptfs/file.c            |   90 ++++++++++++---------------
 fs/ecryptfs/inode.c           |   65 ++++++++++----------
 fs/ecryptfs/main.c            |   23 ++++++-
 fs/ecryptfs/messaging.c       |  136 +++++------------------------------------
 fs/ecryptfs/miscdev.c         |   98 ++++++++---------------------
 fs/ecryptfs/mmap.c            |   39 ++++--------
 7 files changed, 158 insertions(+), 317 deletions(-)

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

                 reply	other threads:[~2012-08-02  6:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20120802060047.GA24033@boyd \
    --to=tyhicks@canonical.com \
    --cc=akpm@linux-foundation.org \
    --cc=ecryptfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.