From: Tyler Hicks <tyhicks@linux.vnet.ibm.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] More eCryptfs fixes
Date: Sun, 29 May 2011 15:01:35 -0500 [thread overview]
Message-ID: <20110529200135.GA9787@boyd.l.tihix.com> (raw)
Hi Linus,
The first 2 patches are code cleanups to pave the way for the 3rd patch,
which fixes a race condition around the i_size field of new eCryptfs
inodes. The last 3 patches are more fs/ecryptfs/inode.c code cleanups
that I couldn't resist doing after I was done fixing the race condition.
Sorry for the late pull request. The reporter of the i_size race
condition was nice enough to test the fix yesterday, but I haven't had
access to a computer until this afternoon.
The following changes since commit 139f37f5e14cd883eee2a8a36289f544b5390a44:
Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/vapier/blackfin (2011-05-28 23:12:28 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ecryptfs/ecryptfs-2.6.git for-linus
Tyler Hicks (6):
eCryptfs: Consolidate inode functions into inode.c
eCryptfs: Cleanup inode initialization code
eCryptfs: Fix new inode race condition
eCryptfs: Return useful code from contains_ecryptfs_marker
eCryptfs: Cleanup and optimize ecryptfs_lookup_interpose()
eCryptfs: Remove ecryptfs_header_cache_2
fs/ecryptfs/crypto.c | 74 +++++------
fs/ecryptfs/ecryptfs_kernel.h | 26 ++---
fs/ecryptfs/file.c | 2 +-
fs/ecryptfs/inode.c | 281 +++++++++++++++++++++++++----------------
fs/ecryptfs/main.c | 84 +------------
fs/ecryptfs/super.c | 16 ---
6 files changed, 220 insertions(+), 263 deletions(-)
reply other threads:[~2011-05-29 20:01 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=20110529200135.GA9787@boyd.l.tihix.com \
--to=tyhicks@linux.vnet.ibm.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
all inboxes | Powered by JetHome®