mm: mempolicy: (Was: add sys_madvise2 and MADV_NAME to name vmas)
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 patch 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | mm: mempolicy: fix mbind_range() && vma_adjust() interactionmm/ mm/ | +6 | 6 replies |
Reviews trailers per patch
The patch has a Reviewed-by or Acked-by.
| Patch | KOSAKI Motohiro |
|---|---|
| 1/1 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/1] mm: mempolicy: (Was: add sys_madvise2 and MADV_NAME to name vmas)
Quoted 6 lines · Colin Cross
Quoted 4 lines · Oleg Nesterov
MADV_NAME(START, PAGE_SIZE, "MY_NAME"); MADV_NAME(START + PAGE_SIZE, PAGE_SIZE, "MY_NAME");
Quoted 6 lines
Quoted 2 lines
The 1st
MADV_NAMEwill split this vma, the 2nd won't merge. Not that I think this is buggy, just a bit inconsistent imho.My intention is that any vmas that would be merged without names would be merged if they have the same name. I copied the logic used for
vm_flags, but I'll take another look.
Please ignore. Sorry I was wrong, I misread this code.
And when I read it now I strongly believe that vma_policy() logic is buggy.
The patch cc's stable but I do not understand mempolicy.c and I have no idea how to test it. So this needs the authoritative acks.
Oleg.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>