[Devel] [PATCH hci-8.1 2/8] oracle/mm: hold the source mmap write lock when copying PTEs

[no-reply at sashiko.virtuozzo.com]

> From: Anthony Yznaga <anthony.yznaga at oracle.com>
> 
> The copy_p*_range() routines assume the mmap write lock is held
> for both the source and destination and therefore there will be
> no unexpected THP transitions while PTEs are copied (for example,
> due to khugepaged). The write lock is already held on the destination
> mm, but until now only the read lock was held on the source.
> 
> Orabug: 38029049
> Signed-off-by: Anthony Yznaga <anthony.yznaga at oracle.com>
> Reviewed-by: Harry Yoo <harry.yoo at oracle.com>
> (cherry picked from commit 285a140316fa44f0cdc6608c109ba525e52d6c3f)
> 
> Taken from Oracle linux-uek branch uek8/u2. Applied cleanly; the only
> change is a trailing space dropped from the new comment in exec_mmap().
> 
> Fixes: 9e6d16a6c0a1 ("oracle/mm: introduce VM_EXEC_KEEP")
> https://virtuozzo.atlassian.net/browse/VSTOR-150231
> 
> Feature: oracle/mm: MADV_DOEXEC madvise() flag
> Assisted-by: LLM
> Signed-off-by: Konstantin Khorenko <khorenko at virtuozzo.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.vzint.dev/#/patchset/20261014-b4-prep-khorenko-vstor-149847-2-doexec-pinned-memory-v1-0-36f1120f9b57@virtuozzo.com?part=2