RFC rework /dev/mem code vs. highmem and DEBUG_VIRTUAL
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest5 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | clean up checks against "high_memory" variablearch/ drivers/ drivers/ +1 more | +21 | 1 reply | |
| 2/5 | make /dev/kmem return error for highmemdrivers/ | +10 | 1 reply | |
| 3/5 | avoid /dev/kmem oopses with DEBUG_VIRTUALdrivers/ | +3 | 0 replies | |
| 4/5 | break up slow_virt_to_phys()arch/ | +26 | 3 replies | |
| 5/5 | keep /dev/kmem from triggering BUG_ON() with DEBUG_VIRTUALarch/ drivers/ include/ | +29 | 1 reply |
Reviews trailers per patch
None of the 5 patches has a Reviewed-by or Acked-by.
| Patch | Borislav Petkov |
|---|---|
| 1/5 | T-b |
| 2/5 | |
| 3/5 | |
| 4/5 | |
| 5/5 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/5] [RFC] rework /dev/mem code vs. highmem and DEBUG_VIRTUAL
/dev/[k]mem are a bit of a mess. They've probably been subtly broken for a long time on highmem or when the kernel's page tables have been munged in other ways.
This has only been lightly tested on x86. Needs some review and some wider testing before getting applied anywhere.