All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tyler Hicks <tyhicks@linux.vnet.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, ecryptfs-devel@lists.launchpad.net
Subject: [GIT PULL] eCryptfs fixes for 2.6.32
Date: Thu, 24 Sep 2009 16:40:51 -0500	[thread overview]
Message-ID: <20090924214049.GA29265@boomer> (raw)

Hi Linus,

The following changes since commit 94e0fb086fc5663c38bbc0fe86d698be8314f82f:
  Linus Torvalds (1):
        Merge branch 'drm-intel-next' of git://git.kernel.org/.../anholt/drm-intel

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/ecryptfs/ecryptfs-2.6.git for-linus

Dave Hansen (1):
      ecryptfs: improved dependency checking and reporting

Roland Dreier (2):
      ecryptfs: Remove unneeded locking that triggers lockdep false positives
      eCryptfs: Fix lockdep-reported AB-BA mutex issue

Tyler Hicks (6):
      eCryptfs: Handle unrecognized tag 3 cipher codes
      eCryptfs: Check for O_RDONLY lower inodes when opening lower files
      eCryptfs: Filename encryption only supports password auth tokens
      eCryptfs: Validate global auth tok keys
      eCryptfs: Propagate vfs_read and vfs_write return codes
      eCryptfs: Prevent lower dentry from going negative during unlink

 fs/ecryptfs/Kconfig      |    4 +++-
 fs/ecryptfs/crypto.c     |   39 ++++++++++++++++++++++-----------------
 fs/ecryptfs/inode.c      |    2 ++
 fs/ecryptfs/keystore.c   |   39 ++++++++++++++++++++++++++-------------
 fs/ecryptfs/kthread.c    |   24 ++++++++----------------
 fs/ecryptfs/main.c       |    3 +--
 fs/ecryptfs/mmap.c       |    4 +++-
 fs/ecryptfs/read_write.c |   32 ++++++++++++--------------------
 fs/ecryptfs/super.c      |    2 --
 9 files changed, 77 insertions(+), 72 deletions(-)

                 reply	other threads:[~2009-09-24 21:40 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=20090924214049.GA29265@boomer \
    --to=tyhicks@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=ecryptfs-devel@lists.launchpad.net \
    --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.