Safely removing mmaped files
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | mm: Introduce revoke_file_mappings.include/ mm/ | +142 | 1 reply | |
| 2/4 | sysfs: Use revoke_file_mappingsfs/ | +13 | 0 replies | |
| 3/4 | proc: Clean up mmaps when a proc file is removed.fs/ | +2 | 0 replies | |
| 4/4 | pci: Remove bogus check of proc dir entry usage.drivers/ | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] Safely removing mmaped files
Currently when mmaped files are removed I have not found a single instance in the kernel where we handle it correctly. Frequently after a hot remove we will either leak a file (with weird ensuing consequences) or we will goof and not call vm_ops->close() which can cause leaks.
It turns out this problem isn't too bad to actually fix and this patchset is my generic solution. Tested against 2.6.31-rc8 with a process that mmaped /sys/*/*/resource0 and /proc/bus/pci/*/*.
I'm not certain what the best way to carry these patches is to get them merged. Andrew can you carry this patchset?
Eric
--
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>