2.6.20 fix for PageUptodate memorder problem (try 3)
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | mm: make read_cache_page synchronousdrivers/ fs/ fs/ +21 more | +68 | 0 replies | |
| 2/3 | fs: buffer don't PageUptodate without page lockedfs/ | +1 | 0 replies | |
| 3/3 | mm: fix PageUptodate memorderfs/ include/ include/ +5 more | +68 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [patch 0/3] 2.6.20 fix for PageUptodate memorder problem (try 3)
OK, I have got rid of SetPageUptodate_nowarn, and removed the atomic op from SetNewPageUptodate. Made PageUptodate_NoLock only issue the memory barrier is the page was uptodate (hopefully the compiler can thread the branch into the caller's branch).
SetNewPageUptodate does not do the S390 page_test_and_clear_dirty, so I'd like to make sure that's OK.
Rearranged the patch series so we don't have the first patch introducing a lot of WARN_ONs that are solved in the next two patches (rather, solve those issues first).
Thanks,
Nick
--
SuSE Labs
--
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>