diff options
| author | Kefeng Wang <wangkefeng.wang@huawei.com> | 2024-10-28 22:56:55 +0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-12-27 14:02:20 +0100 |
| commit | b79b6fe0737f233f0be1465052b7f0e75f324735 (patch) | |
| tree | 682b69aecfbb8de8cf6ac6896f3af547a5ab110b /scripts/const_structs.checkpatch | |
| parent | eb9041837123f31d5897e99bb761f46cb4ce5859 (diff) | |
| download | linux-b79b6fe0737f233f0be1465052b7f0e75f324735.tar.gz linux-b79b6fe0737f233f0be1465052b7f0e75f324735.tar.bz2 linux-b79b6fe0737f233f0be1465052b7f0e75f324735.zip | |
mm: use aligned address in clear_gigantic_page()
commit 8aca2bc96c833ba695ede7a45ad7784c836a262e upstream.
In current kernel, hugetlb_no_page() calls folio_zero_user() with the
fault address. Where the fault address may be not aligned with the huge
page size. Then, folio_zero_user() may call clear_gigantic_page() with
the address, while clear_gigantic_page() requires the address to be huge
page size aligned. So, this may cause memory corruption or information
leak, addtional, use more obvious naming 'addr_hint' instead of 'addr' for
clear_gigantic_page().
Link: https://lkml.kernel.org/r/20241028145656.932941-1-wangkefeng.wang@huawei.com
Fixes: 78fefd04c123 ("mm: memory: convert clear_huge_page() to folio_zero_user()")
Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
Reviewed-by: "Huang, Ying" <ying.huang@intel.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
Cc: Muchun Song <muchun.song@linux.dev>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts/const_structs.checkpatch')
0 files changed, 0 insertions, 0 deletions