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.6-rc6
Date: Fri, 14 Sep 2012 10:24:09 -0700 [thread overview]
Message-ID: <20120914172408.GA22346@boyd> (raw)
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
Hi Linus,
The following changes since commit e9bd8f1624cb0f647867d6cced79cb26ef3651bf:
Merge branch 'for-linus' of git://git.samba.org/sfrench/cifs-2.6 (2012-09-11 05:52:49 +0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git tags/ecryptfs-3.6-rc6-fixes
for you to fetch changes up to 8335eafc2859e1a26282bef7c3d19f3d68868b8a:
eCryptfs: Copy up attributes of the lower target inode after rename (2012-09-14 09:36:03 -0700)
----------------------------------------------------------------
- Fixes a regression, introduced in 3.6-rc1, when a file is closed before its
shared memory mapping is dirtied and unmapped. The lower file was being
released when the eCryptfs file was closed and the dirtied pages could not be
written out.
- Adds a call to the lower filesystem's ->flush() from ecryptfs_flush().
- Fixes a regression, introduced in 2.6.39, when a file is renamed on top of
another file. The target file's inode was not being evicted and the space
taken by the file was not reclaimed until eCryptfs was unmounted.
----------------------------------------------------------------
Tyler Hicks (3):
eCryptfs: Write out all dirty pages just before releasing the lower file
eCryptfs: Call lower ->flush() from ecryptfs_flush()
eCryptfs: Copy up attributes of the lower target inode after rename
fs/ecryptfs/file.c | 10 ++++++++--
fs/ecryptfs/inode.c | 5 +++++
fs/ecryptfs/main.c | 1 +
3 files changed, 14 insertions(+), 2 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2012-09-14 17:24 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=20120914172408.GA22346@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;
as well as URLs for NNTP newsgroup(s).