The patch titled
eCryptfs: increment extent_offset once per loop interation
has been removed from the -mm tree. Its filename was
ecryptfs-increment-extent_offset-once-per-loop-interation.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: eCryptfs: increment extent_offset once per loop interation
From: Michael Halcrow <[EMAIL PROTECTED]>
The extent_offset is getting incremented twice per loop iteration through any
given page. It should only be getting incremented once. This bug should only
impact hosts with >4K page sizes.
Signed-off-by: Michael Halcrow <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
fs/ecryptfs/crypto.c | 2 --
1 file changed, 2 deletions(-)
diff -puN
fs/ecryptfs/crypto.c~ecryptfs-increment-extent_offset-once-per-loop-interation
fs/ecryptfs/crypto.c
---
a/fs/ecryptfs/crypto.c~ecryptfs-increment-extent_offset-once-per-loop-interation
+++ a/fs/ecryptfs/crypto.c
@@ -504,7 +504,6 @@ int ecryptfs_encrypt_page(struct page *p
"\n", rc);
goto out;
}
- extent_offset++;
}
out:
kfree(enc_extent_virt);
@@ -640,7 +639,6 @@ int ecryptfs_decrypt_page(struct page *p
"rc = [%d]\n", __FUNCTION__, rc);
goto out;
}
- extent_offset++;
}
out:
kfree(enc_extent_virt);
_
Patches currently in -mm which might be from [EMAIL PROTECTED] are
origin.patch
ecryptfs-cast-page-index-to-loff_t-instead-of-off_t.patch
git-unionfs.patch
pagecache-zeroing-zero_user_segment-zero_user_segments-and-zero_user.patch
fs-ecryptfs-possible-cleanups.patch
ecryptfs-track-header-bytes-rather-than-extents.patch
ecryptfs-set-inode-key-only-once-per-crypto-operation.patch
d_path-make-d_path-use-a-struct-path.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
