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.3-rc4
Date: Thu, 16 Feb 2012 18:31:29 -0600 [thread overview]
Message-ID: <20120217003128.GA20071@boyd> (raw)
[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]
The following changes since commit c38e23456278e967f094b08247ffc3711b1029b2:
i387: fix sense of sanity check (2012-02-15 08:05:18 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git ecryptfs-3.3-rc4-fixes
for you to fetch changes up to 465c9343c5b746ec2325a220fa3e50cc647d2db7:
ecryptfs: remove the second argument of k[un]map_atomic() (2012-02-16 16:06:27 -0600)
----------------------------------------------------------------
Fixes maximum filename length and filesystem type reporting in statfs() calls
and also fixes stale inode mode bits on eCryptfs inodes after a POSIX ACL was
set on the lower filesystem's inode.
----------------------------------------------------------------
Cong Wang (1):
ecryptfs: remove the second argument of k[un]map_atomic()
Tyler Hicks (2):
eCryptfs: Improve statfs reporting
eCryptfs: Copy up lower inode attrs after setting lower xattr
fs/ecryptfs/crypto.c | 68 ++++++++++++++++++++++++++++++++++++----
fs/ecryptfs/ecryptfs_kernel.h | 6 +++
fs/ecryptfs/inode.c | 2 +
fs/ecryptfs/keystore.c | 9 ++---
fs/ecryptfs/mmap.c | 4 +-
fs/ecryptfs/read_write.c | 4 +-
fs/ecryptfs/super.c | 14 ++++++++-
7 files changed, 89 insertions(+), 18 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2012-02-17 0:31 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=20120217003128.GA20071@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.