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.19-rc1
Date: Fri, 19 Dec 2014 12:11:47 -0600	[thread overview]
Message-ID: <20141219181146.GA6629@boyd> (raw)

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

Hi Linus,

The following changes since commit c3351dfabf5c78fb5ddc79d0f7b65ebd9e441337:

  Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending (2014-10-21 13:06:38 -0700)

are available in the git repository at:

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

for you to fetch changes up to 942080643bce061c3dd9d5718d3b745dcb39a8bc:

  eCryptfs: Remove buggy and unnecessary write in file name decode routine (2014-11-26 15:55:02 -0600)

----------------------------------------------------------------
Fixes for filename decryption and encrypted view plus a cleanup
- The filename decryption routines were, at times, writing a zero byte one
  character past the end of the filename buffer
- The encrypted view feature attempted, and failed, to roll its own form of
  enforcing a read-only mount instead of letting the VFS enforce it

----------------------------------------------------------------
Michael Halcrow (1):
      eCryptfs: Remove buggy and unnecessary write in file name decode routine

Tyler Hicks (2):
      eCryptfs: Force RO mount when encrypted view is enabled
      eCryptfs: Remove unnecessary casts when parsing packet lengths

 fs/ecryptfs/crypto.c   |  1 -
 fs/ecryptfs/file.c     | 12 ------------
 fs/ecryptfs/keystore.c |  6 +++---
 fs/ecryptfs/main.c     | 16 +++++++++++++---
 4 files changed, 16 insertions(+), 19 deletions(-)

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

                 reply	other threads:[~2014-12-19 18:11 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=20141219181146.GA6629@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.