Re: mmotm 2021-05-12-21-46 uploaded (mm/memory_failure.c)
From: Randy Dunlap <hidden>
Date: 2021-05-13 05:28:42
Also in:
linux-fsdevel, linux-mm, lkml, mm-commits
From: Randy Dunlap <hidden>
Date: 2021-05-13 05:28:42
Also in:
linux-fsdevel, linux-mm, lkml, mm-commits
On 5/12/21 9:47 PM, akpm@linux-foundation.org wrote:
The mm-of-the-moment snapshot 2021-05-12-21-46 has been uploaded to https://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: https://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You will need quilt to apply these patches to the latest Linus release (5.x or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in https://ozlabs.org/~akpm/mmotm/series The file broken-out.tar.gz contains two datestamp files: .DATE and .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss, followed by the base kernel version against which this patch series is to be applied. This tree is partially included in linux-next. To see which patches are included in linux-next, consult the `series' file. Only the patches within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in linux-next.
on x86_64:
# CONFIG_HUGETLBFS is not set
../mm/memory-failure.c: In function ‘__get_hwpoison_page’:
../mm/memory-failure.c:962:15: error: ‘hugetlb_lock’ undeclared (first use in this function); did you mean ‘huge_pte_lock’?
spin_lock(&hugetlb_lock);
^~~~~~~~~~~~
--
~Randy
Reported-by: Randy Dunlap <redacted>