{"push_id":2399432697,"size":1,"distinct_size":1,"ref":"refs/heads/aosp-common/upstream-f2fs-stable-linux-4.4.y","head":"39ed8376d611d2a211079be6a2ac08715f5a58c4","before":"5f9b3abb911fa2f51f5690f4376cf919c2069662","commits":[{"sha":"39ed8376d611d2a211079be6a2ac08715f5a58c4","author":{"name":"Yunlong Song","email":"7108849fa5369d74ce1e809d043225672bdfb817@huawei.com"},"message":"f2fs: don't put dentry page in pagecache into highmem\n\nPrevious dentry page uses highmem, which will cause panic in platforms\nusing highmem (such as arm), since the address space of dentry pages\nfrom highmem directly goes into the decryption path via the function\nfscrypt_fname_disk_to_usr. But sg_init_one assumes the address is not\nfrom highmem, and then cause panic since it doesn't call kmap_high but\nkunmap_high is triggered at the end. To fix this problem in a simple\nway, this patch avoids to put dentry page in pagecache into highmem.\n\nSigned-off-by: Yunlong Song <yunlong.song@huawei.com>\nReviewed-by: Chao Yu <yuchao0@huawei.com>\n[Jaegeuk Kim: fix coding style]\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/codeaurora-unofficial/kernel-msm/commits/39ed8376d611d2a211079be6a2ac08715f5a58c4"}]}
{"actor":{"display_login":"Mazda--"}}