Fix read-only THP for non-tmpfs filesystems
Status from this message: [merged] mm-filemap-fix-storing-to-a-thp-shadow-entry.patch removed from -mm tree
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 All 3 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | XArray: Add xa_get_orderinclude/ lib/ lib/ | +69 | 0 replies | Applied |
| 2/3 | XArray: Add xas_splitDocumentation/ include/ lib/ +1 more | +211 | 0 replies | Applied |
| 3/3 | mm/filemap: Fix storing to a THP shadow entrymm/ | +31 | 0 replies | Applied |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] Fix read-only THP for non-tmpfs filesystems
As described more verbosely in the [3/3] changelog, we can inadvertently put an order-0 page in the page cache which occupies 512 consecutive entries. Users are running into this if they enable the READ_ONLY_THP_FOR_FS config option; see https://bugzilla.kernel.org/show_bug.cgi?id=206569
and Qian Cai has also reported it here:
https://lore.kernel.org/lkml/[email protected]/
This is a rather intrusive way of fixing the problem, but has the advantage that I've actually been testing it with the THP patches, which means that it sees far more use than it does upstream -- indeed, Song has been entirely unable to reproduce it. It also has the advantage that it removes a few patches from my gargantuan backlog of THP patches.
Matthew Wilcox (Oracle) (3):
XArray: Add xa_get_order
XArray: Add xas_split
mm/filemap: Fix storing to a THP shadow entry
Documentation/core-api/xarray.rst | 16 +-- include/linux/xarray.h | 22 ++++ lib/test_xarray.c | 62 ++++++++++ lib/xarray.c | 196 ++++++++++++++++++++++++++++-- mm/filemap.c | 42 +++++-- 5 files changed, 311 insertions(+), 27 deletions(-)
Signature · 1 line
2.28.0