Re: [PATCH] f2fs: don't put dentry page in pagecache into highmem

2018-03-18 Thread Yunlong Song
OK, got it. On 2018/3/19 14:23, Jaegeuk Kim wrote: On 03/19, Yunlong Song wrote: Hi, Jaegeuk, I find this patch is removed from current branch of dev-test recently, why? Any bugs? Moved into the beginning of the tree for cherry-picking into f2fs-stable. Thanks, On 2018/2/28 20:31, Yunl

Re: [PATCH] f2fs: don't put dentry page in pagecache into highmem

2018-03-18 Thread Jaegeuk Kim
On 03/19, Yunlong Song wrote: > Hi, Jaegeuk, > I find this patch is removed from current branch of dev-test > recently, why? Any bugs? Moved into the beginning of the tree for cherry-picking into f2fs-stable. Thanks, > > On 2018/2/28 20:31, Yunlong Song wrote: > > Previous dentry page uses

Re: [PATCH] f2fs: don't put dentry page in pagecache into highmem

2018-03-18 Thread Yunlong Song
Hi, Jaegeuk, I find this patch is removed from current branch of dev-test recently, why? Any bugs? On 2018/2/28 20:31, Yunlong Song wrote: Previous dentry page uses highmem, which will cause panic in platforms using highmem (such as arm), since the address space of dentry pages from highmem

Re: [PATCH] f2fs: don't put dentry page in pagecache into highmem

2018-02-28 Thread Chao Yu
On 2018/2/28 20:31, Yunlong Song wrote: > Previous dentry page uses highmem, which will cause panic in platforms > using highmem (such as arm), since the address space of dentry pages > from highmem directly goes into the decryption path via the function > fscrypt_fname_disk_to_usr. But sg_init_one

[PATCH] f2fs: don't put dentry page in pagecache into highmem

2018-02-28 Thread Yunlong Song
Previous dentry page uses highmem, which will cause panic in platforms using highmem (such as arm), since the address space of dentry pages from highmem directly goes into the decryption path via the function fscrypt_fname_disk_to_usr. But sg_init_one assumes the address is not from highmem, and th