Messages in this thread | | | Date | Fri, 28 Apr 2023 21:39:57 +0100 | From | Conor Dooley <> | Subject | Re: [PATCH -fixes 1/2] riscv: Fix huge_ptep_set_wrprotect when PTE is a NAPOT |
| |
On Fri, Apr 28, 2023 at 02:01:19PM +0200, Alexandre Ghiti wrote: > We need to avoid inconsistencies across the PTEs that form a NAPOT > region, so when we write protect such a region, we should clear and flush > all the PTEs to make sure that any of those PTEs is not cached which would > result in such inconsistencies (arm64 does the same). > > Fixes: f2aeb0118ddd ("riscv: mm: support Svnapot in hugetlb page")
For both patches I get: Commit: 0146c955ff59 ("riscv: Fix huge_ptep_set_wrprotect when PTE is a NAPOT") Fixes tag: Fixes: f2aeb0118ddd ("riscv: mm: support Svnapot in hugetlb page") Has these problem(s): - Target SHA1 does not exist
This particular one is 82a1a1f3bfb6 in riscv/for-next.
Cheers, Conor. [unhandled content-type:application/pgp-signature] | |