The patch titled
     eCryptfs: cast page->index to loff_t instead of off_t
has been added to the -mm tree.  Its filename is
     ecryptfs-cast-page-index-to-loff_t-instead-of-off_t.patch

*** Remember to use Documentation/SubmitChecklist when testing your code ***

See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this

------------------------------------------------------
Subject: eCryptfs: cast page->index to loff_t instead of off_t
From: Michael Halcrow <[EMAIL PROTECTED]>

page->index should be cast to loff_t instead of off_t.

Signed-off-by: Michael Halcrow <[EMAIL PROTECTED]>
Reported-by: Eric Sandeen <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 fs/ecryptfs/read_write.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff -puN 
fs/ecryptfs/read_write.c~ecryptfs-cast-page-index-to-loff_t-instead-of-off_t 
fs/ecryptfs/read_write.c
--- 
a/fs/ecryptfs/read_write.c~ecryptfs-cast-page-index-to-loff_t-instead-of-off_t
+++ a/fs/ecryptfs/read_write.c
@@ -87,7 +87,7 @@ int ecryptfs_write_lower_page_segment(st
        loff_t offset;
        int rc;
 
-       offset = ((((off_t)page_for_lower->index) << PAGE_CACHE_SHIFT)
+       offset = ((((loff_t)page_for_lower->index) << PAGE_CACHE_SHIFT)
                  + offset_in_page);
        virt = kmap(page_for_lower);
        rc = ecryptfs_write_lower(ecryptfs_inode, virt, offset, size);
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

ecryptfs-increment-extent_offset-once-per-loop-interation.patch
ecryptfs-release-mutex-on-hash-error-path.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

Reply via email to