on do_page_fault() and *copy*_inatomic
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | mm: arch do_page_fault() vs in_atomic()arch/ arch/ arch/ +5 more | +8 | 0 replies | |
| 2/3 | mm: pagefault_{disable,enable}()arch/ arch/ arch/ +14 more | +87 | 0 replies | |
| 3/3 | mm: k{,um}map_atomic() vs in_atomic()include/ include/ | +13 | 0 replies |
Reviews trailers per patch
All 3 patches have a Reviewed-by or Acked-by.
| Patch | Nick Piggin |
|---|---|
| 1/3 | A-b |
| 2/3 | A-b |
| 3/3 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3] on do_page_fault() and *copy*_inatomic
In light of the recent work on fault handlers and generic_file_buffered_write() I've gone over some of the arch specific stuff that supports this work.
The following three patches are ready for inclusion IMHO, please apply.
The first patch fixes up some arch fault handlers to respect the 'take no locks in atomic context' rule; this also fixes CONFIG_PREEMPT bugs on those platforms.
The second patch introduces pagefault_{disable,enable}() - an abtraction that replaces the now open coded {inc,dec}_preempt_count() calls when we mean to create atomic pagefault scope. The added barrier() calls in the new primitives might fix some CONFIG_PREEMPT bugs.
The third patch make k{,un}map_atomic denote an atomic pagefault scope. All non-trivial implementation already do this, and this allows us to rely on that in generic. This might also fix some bugs where people already assumed this.
Peter
--
--
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>