public inbox for linux-kernel@vger.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.2-rc3
Date: Wed, 23 Nov 2011 16:25:55 -0600	[thread overview]
Message-ID: <20111123222555.GA1094@boyd> (raw)

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

Hi Linus - Here are 3 eCryptfs fixes. The first patch solves a race condition
around the initialization of eCryptfs inode info. The second patch solves a
regression in mmap support. The last patch fixes a kernel memory disclosure
which was fixed using your suggested implementation.

The following changes since commit 6fe4c6d466e95d31164f14b1ac4aefb51f0f4f82:

  Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2011-11-20 14:59:33 -0800)

are available in the git repository at:

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

Tyler Hicks (3):
      eCryptfs: Prevent file create race condition
      eCryptfs: Flush file in vma close
      eCryptfs: Extend array bounds for all filename chars

 fs/ecryptfs/crypto.c          |   26 +++++++++++---------
 fs/ecryptfs/ecryptfs_kernel.h |    5 ++-
 fs/ecryptfs/file.c            |   23 +++++++++++++++++-
 fs/ecryptfs/inode.c           |   52 ++++++++++++++++++++++++----------------
 4 files changed, 70 insertions(+), 36 deletions(-)

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

             reply	other threads:[~2011-11-23 22:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 22:25 Tyler Hicks [this message]
2011-11-23 22:56 ` [GIT PULL] eCryptfs fixes for 3.2-rc3 Linus Torvalds
2011-11-24  7:45   ` Tyler Hicks
2011-11-24 18:27     ` Linus Torvalds

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=20111123222555.GA1094@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox