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-rc2
Date: Wed, 25 Jan 2012 16:12:50 -0600 [thread overview]
Message-ID: <20120125221249.GH16865@boyd> (raw)
[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]
Hi Linus - Here's a pile of eCryptfs bug fixes.
Tim's logging message update will be really helpful to users when
they're trying to locate a problematic file in the lower filesystem with
filename encryption enabled.
You'll recognize the fix from Li, as you commented on that.
You should also be familiar with my setattr/truncate improvements, since
you were the one that pointed them out to us (thanks again!). Andrew
noted the /dev/ecryptfs write count sanitization needed to be improved,
so I've got a fix in there for that along with some other less important
cleanups of the /dev/ecryptfs read/write code.
They've all sat in -next for at least a day, while some have been there
around a week, I believe.
I'll get signed tags going for the next pull request I send. That was my
intention this time, but it just hit me that I forgot to do it.
Thanks,
Tyler
The following changes since commit dcd6c92267155e70a94b3927bce681ce74b80d1f:
Linux 3.3-rc1 (2012-01-19 15:04:48 -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
Li Wang (1):
eCryptfs: Infinite loop due to overflow in ecryptfs_write()
Tim Gardner (2):
ecryptfs: Improve metadata read failure logging
ecryptfs: Remove unnecessary variable initialization
Tyler Hicks (7):
eCryptfs: Sanitize write counts of /dev/ecryptfs
eCryptfs: Report errors in writes to /dev/ecryptfs
eCryptfs: Replace miscdev read/write magic numbers
eCryptfs: Make truncate path killable
eCryptfs: Check inode changes in setattr
eCryptfs: Remove unused ecryptfs_read()
eCryptfs: Fix oops when printing debug info in extent crypto functions
MAINTAINERS | 2 +-
fs/ecryptfs/crypto.c | 54 +++-------------
fs/ecryptfs/ecryptfs_kernel.h | 5 ++
fs/ecryptfs/inode.c | 48 +++++++++++----
fs/ecryptfs/keystore.c | 5 +-
fs/ecryptfs/miscdev.c | 140 +++++++++++++++++++++++++----------------
fs/ecryptfs/read_write.c | 96 +++++-----------------------
7 files changed, 155 insertions(+), 195 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2012-01-25 22:12 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=20120125221249.GH16865@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.