mm/huge_memory: couple fixes and one cleanup
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 8 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mm/huge_memory: skip invalid debugfs file entry for folio splitmm/ | +9 | 6 replies | |
| 2/2 | mm/huge_memory: cap max length on debugfs file entry folio splitmm/ | +6 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] mm/huge_memory: couple fixes and one cleanup
I've been stress testing large folio splits using the new debugfs interface with a new fstests test [0], to make the debugfs interface more useful it helps to do bounds checks on input parameters so this fixes two issues found while doing automatic stress testing of the debugfs interface with found files.
Provided there are no issues I think this should go in for v6.9-rc6.
Also, *should* we strive to support splits for large folios to min order with say MADV_NOHUGEPAGE ?
[0] https://lkml.kernel.org/r/[email protected]
Luis Chamberlain (2):
mm/huge_memory: skip invalid debugfs file entry for folio split mm/huge_memory: cap max length on debugfs file entry folio split
mm/huge_memory.c | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-)
Signature · 1 line
2.43.0