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 fix for 3.2-rc7
Date: Thu, 22 Dec 2011 14:56:26 -0600 [thread overview]
Message-ID: <20111222205626.GB1927@boyd> (raw)
[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]
Hi Linus - Here is a fix for ecryptfs_statfs(). It had simply deferred
to the lower filesystem's statfs(), but the filename encryption feature
significantly reduces the max filename length. There are a few
applications that have trouble with the filename length limitation and I
think exposing the maximum length in statfs() calls is the first step in
improving the situation.
I'm a little torn on whether the fix needs to go in so late in the
cycle, but I feel it is low risk. If you disagree, I have no problem
waiting for 3.3.
The other patch is an update to Dustin's email address in MAINTAINERS.
The following changes since commit 511585a28e5b5fd1cac61e601e42efc4c5dd64b5:
Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband (2011-12-19 15:13:53 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git for-linus
Dustin Kirkland (1):
MAINTAINERS: Update eCryptfs maintainer address
Tyler Hicks (1):
eCryptfs: Improve statfs reporting
MAINTAINERS | 2 +-
fs/ecryptfs/crypto.c | 68 ++++++++++++++++++++++++++++++++++++----
fs/ecryptfs/ecryptfs_kernel.h | 5 +++
fs/ecryptfs/keystore.c | 9 ++---
fs/ecryptfs/super.c | 14 ++++++++-
5 files changed, 83 insertions(+), 15 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2011-12-22 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 20:56 Tyler Hicks [this message]
2011-12-22 21:00 ` [GIT PULL] eCryptfs fix for 3.2-rc7 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=20111222205626.GB1927@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