v3
2026-08-03
全配置启用 per-VMA 锁并清理 · v3
让 per-VMA 锁在所有配置下可用,减少 #ifdef,并简化 binder 等调用方,新增无需 mmap_lock 回退的辅助 API。
原始补丁链接
子 Patch(5)
1/5
mm: Make per-VMA locks available universally
[mm: Make per-VMA locks available universally] From: Dave Hansen dave.hansen@linux.intel.com The per-VMA locks have been around for several years. They’ve had some bugs worked out of them and have
2/5
binder: Make shrinker rely solely on per-VMA lock
[binder: Make shrinker rely solely on per-VMA lock] From: Dave Hansen dave.hansen@linux.intel.com tl;dr: lock_vma_under_rcu() is already a trylock. No need to do both it and mmap_read_trylock(). L
3/5
mm: Add RCU-based VMA lookup helper that waits for writers
[mm: Add RCU-based VMA lookup helper that waits for writers] From: Dave Hansen dave.hansen@linux.intel.com == Background == There are basically two parallel ways to look up a VMA: the traditional
4/5
binder: Remove mmap_lock fallback
[binder: Remove mmap_lock fallback] From: Dave Hansen dave.hansen@linux.intel.com Previously, the per-VMA locking could fail in the face of writers which necessitate a fallback to mmap_lock. The ne
5/5
tcp: Remove mmap_lock fallback path
[tcp: Remove mmap_lock fallback path] From: Dave Hansen dave.hansen@linux.intel.com Previously, the per-VMA locking could fail in the face of writers which necessitates a fallback to mmap_lock. The