RFC HWPOISON incremental fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest5 patches 36 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | HWPOISON: define VM_FAULT_HWPOISON to 0 when feature is disabledarch/ include/ | +7 | 23 replies | |
| 2/5 | HWPOISON: fix tasklist_lock/anon_vma locking ordermm/ | +6 | 5 replies | |
| 3/5 | HWPOISON: remove early kill option for nowDocumentation/ include/ include/ +4 more | +3 | 2 replies | |
| 4/5 | HWPOISON: report sticky EIO for poisoned fileinclude/ mm/ mm/ | +25 | 3 replies | |
| 5/5 | HWPOISON: use the safer invalidate page for possible metadata pagesinclude/ mm/ mm/ | +15 | 1 reply |
Reviews trailers per patch
All 5 patches have a Reviewed-by or Acked-by.
| Patch | Rik van Riel |
|---|---|
| 1/5 | A-b |
| 2/5 | A-b |
| 3/5 | A-b |
| 4/5 | A-b |
| 5/5 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/5] [RFC] HWPOISON incremental fixes
Hi all,
Here are the hwpoison fixes that aims to address Nick and Hugh's concerns. Note that
- the early kill option is dropped for .31. It's obscure option and complex code and is not must have for .31. Maybe Andi also aims this option for notifying KVM, but right now KVM is not ready to handle that.
- It seems that even fsync() processes are not easy to catch, so I abandoned the SIGKILL on fsync() idea. Instead, I choose to fail any attempt to populate the poisoned file with new pages, so that the corrupted page offset won't be repopulated with outdated data. This seems to be a safe way to allow the process to continue running while still be able to promise good (but not complete) data consistency.
- I didn't implement the PANIC-on-corrupted-data option. Instead, I guess sending uevent notification to user space will be a more flexible scheme?
Thanks,
Fengguang
Signature · 5 lines
-- 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>