The patch titled affs: use zero_user_page has been added to the -mm tree. Its filename is affs-use-zero_user_page.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: affs: use zero_user_page From: Nate Diller <nate.diller@xxxxxxxxx> Use zero_user_page() instead of open-coding it. Signed-off-by: Nate Diller <nate.diller@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- fs/affs/file.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff -puN fs/affs/file.c~affs-use-zero_user_page fs/affs/file.c --- a/fs/affs/file.c~affs-use-zero_user_page +++ a/fs/affs/file.c @@ -628,11 +628,7 @@ static int affs_prepare_write_ofs(struct return err; } if (to < PAGE_CACHE_SIZE) { - char *kaddr = kmap_atomic(page, KM_USER0); - - memset(kaddr + to, 0, PAGE_CACHE_SIZE - to); - flush_dcache_page(page); - kunmap_atomic(kaddr, KM_USER0); + zero_user_page(page, to, PAGE_CACHE_SIZE - to, KM_USER0); if (size > offset + to) { if (size < offset + PAGE_CACHE_SIZE) tmp = size & ~PAGE_CACHE_MASK; _ Patches currently in -mm which might be from nate.diller@xxxxxxxxx are cifs-use-simple_prepare_write-to-zero-page-data.patch ext4-use-simple_prepare_write-to-zero-page-data.patch fs-convert-core-functions-to-zero_user_page.patch fs-convert-core-functions-to-zero_user_page-pass-kmap-type.patch affs-use-zero_user_page.patch ecryptfs-use-zero_user_page.patch ext3-use-zero_user_page.patch ext4-use-zero_user_page.patch gfs2-use-zero_user_page.patch nfs-use-zero_user_page.patch ntfs-use-zero_user_page.patch ocfs2-use-zero_user_page.patch reiserfs-use-zero_user_page.patch xfs-use-zero_user_page.patch fs-deprecate-memclear_highpage_flush.patch reiser4-use-zero_user_page.patch reiser4-use-simple_prepare_write-to-zero-page-data.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