Fix issues with vmalloc flush flag
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v5 Latest2 patches 3 repliesIn review
- v42 patches 3 repliesSuperseded
- v2 posting 2/22 patches 5 repliesSuperseded
Earlier versions · 2
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v2 posting 1/2 | 1 patch | 14 replies | Superseded | |
| v1 | 1 patch | 2 replies | Superseded |
Changes in v5 from the cover letter
- Update commit messages with info that the first issue will actually not cause problems today
- Avoid re-use of variable (PeterZ)
Patches in v5 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | vmalloc: Fix calculation of direct map addr rangemm/ | +6 | 0 replies | |
| 2/2 | vmalloc: Avoid rare case of flushing tlb with weird argumentsmm/ | +3 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v5 yet.
Cover letter [PATCH v5 0/2] Fix issues with vmalloc flush flag
These two patches address issues with the recently added VM_FLUSH_RESET_PERMS vmalloc flag.
Patch 1 addresses an issue that could cause a crash after other architectures besides x86 rely on this path.
Patch 2 addresses an issue where in a rare case strange arguments could be provided to flush_tlb_kernel_range().
v4->v5:
- Update commit messages with info that the first issue will actually not cause problems today
- Avoid re-use of variable (PeterZ)
v3->v4:
- Drop patch that switched vm_unmap_alias() calls to regular flush (Andy)
- Add patch to address correctness previously fixed in dropped patch
v2->v3:
- Split into two patches (Andy)
v1->v2:
- Update commit message with more detail
- Fix flush end range on !CONFIG_ARCH_HAS_SET_DIRECT_MAP case
Rick Edgecombe (2):
vmalloc: Fix calculation of direct map addr range
vmalloc: Avoid rare case of flushing tlb with weird arguments
mm/vmalloc.c | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-)
Signature · 1 line
2.20.1