The patch titled
eCryptfs: set O_LARGEFILE when opening lower file
has been removed from the -mm tree. Its filename was
ecryptfs-set-o_largefile-when-opening-lower-file.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: eCryptfs: set O_LARGEFILE when opening lower file
From: Michael Halcrow <mhalcrow@xxxxxxxxxx>
O_LARGEFILE should be set here when opening the lower file.
Signed-off-by: Michael Halcrow <mhalcrow@xxxxxxxxxx>
Cc: Dmitriy Monakhov <dmonakhov@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/ecryptfs/file.c | 1 +
fs/ecryptfs/inode.c | 3 ---
2 files changed, 1 insertion(+), 3 deletions(-)
diff -puN fs/ecryptfs/file.c~ecryptfs-set-o_largefile-when-opening-lower-file fs/ecryptfs/file.c
--- a/fs/ecryptfs/file.c~ecryptfs-set-o_largefile-when-opening-lower-file
+++ a/fs/ecryptfs/file.c
@@ -205,6 +205,7 @@ int ecryptfs_open_lower_file(struct file
{
int rc = 0;
+ flags |= O_LARGEFILE;
dget(lower_dentry);
mntget(lower_mnt);
*lower_file = dentry_open(lower_dentry, lower_mnt, flags);
diff -puN fs/ecryptfs/inode.c~ecryptfs-set-o_largefile-when-opening-lower-file fs/ecryptfs/inode.c
--- a/fs/ecryptfs/inode.c~ecryptfs-set-o_largefile-when-opening-lower-file
+++ a/fs/ecryptfs/inode.c
@@ -200,9 +200,6 @@ static int ecryptfs_initialize_file(stru
inode = ecryptfs_dentry->d_inode;
crypt_stat = &ecryptfs_inode_to_private(inode)->crypt_stat;
lower_flags = ((O_CREAT | O_TRUNC) & O_ACCMODE) | O_RDWR;
-#if BITS_PER_LONG != 32
- lower_flags |= O_LARGEFILE;
-#endif
lower_mnt = ecryptfs_dentry_to_lower_mnt(ecryptfs_dentry);
/* Corresponding fput() at end of this function */
if ((rc = ecryptfs_open_lower_file(&lower_file, lower_dentry, lower_mnt,
_
Patches currently in -mm which might be from mhalcrow@xxxxxxxxxx are
origin.patch
ecryptfs-check-xattr-operation-support-fix.patch
git-unionfs.patch
ecryptfs-handles-aop_truncated_page-better.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
