Some cleanups for page isolation
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | mm: check negative error of folio_isolate_lru() when failed to isolate a foliomm/ mm/ mm/ | +3 | 0 replies | |
| 2/3 | mm: check negative error of isolate_lru_page() when failed to isolate a pagemm/ mm/ mm/ +1 more | +5 | 0 replies | |
| 3/3 | mm: mempolicy: check negative error of isolate_hugetlb() when failed to isolate a hugetlbmm/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] Some cleanups for page isolation
Hi,
The page isolation functions did not return a boolean to indicate success or not, instead it will return a negative error when failed to isolate a page. So it's better to check the negative error explicitly for isolation to make the code more clear per Linus's suggestion in [1].
No functional changes intended in this patch series.
Baolin Wang (3):
mm: check negative error of folio_isolate_lru() when failed to isolate
a folio
mm: check negative error of isolate_lru_page() when failed to isolate
a page
mm: mempolicy: check negative error of isolate_hugetlb() when failed
to isolate a hugetlb
mm/damon/paddr.c | 2 +- mm/gup.c | 2 +- mm/khugepaged.c | 4 ++-- mm/memcontrol.c | 2 +- mm/mempolicy.c | 2 +- mm/migrate.c | 4 ++-- mm/migrate_device.c | 2 +- 7 files changed, 9 insertions(+), 9 deletions(-)
Signature · 1 line
2.27.0