xfs: Fix races between readahead and hole punching
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest3 patches 15 repliesIn review
- v13 patches 9 repliesSuperseded
Changes in v2 from the cover letter
* Added reviewed-by tags
* Fixed indentation in xfs_file_fadvise()
* Improved comment and readibility of xfs_file_fadvise()
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | mm: Handle MADV_WILLNEED through vfs_fadvise()mm/ | +16 | 1 reply | |
| 2/3 | fs: Export generic_fadvise()include/ mm/ | +4 | 0 replies | |
| 3/3 | xfs: Fix stale data exposure when readahead races with hole punchfs/ | +26 | 8 replies |
Reviews trailers per patch
All 3 patches have a Reviewed-by or Acked-by.
| Patch | Boaz Harrosh | Darrick J. Wong |
|---|---|---|
| 1/3 | R-b | R-b |
| 2/3 | R-b | |
| 3/3 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3 v2] xfs: Fix races between readahead and hole punching
Hello,
this is a patch series that addresses a possible race between readahead and hole punching Amir has discovered [1]. The first patch makes madvise(2) to handle readahead requests through fadvise infrastructure, the third patch then adds necessary locking to XFS to protect against the race. Note that other filesystems need similar protections but e.g. in case of ext4 it isn't so simple without seriously regressing mixed rw workload performance so I'm pushing just xfs fix at this moment which is simple.
Changes since v1 (posted at [2]):
* Added reviewed-by tags
* Fixed indentation in xfs_file_fadvise()
* Improved comment and readibility of xfs_file_fadvise()
Honza
[1] https://lore.kernel.org/linux-fsdevel/CAOQ4uxjQNmxqmtA_VbYW0Su9rKRk2zobJmahcyeaEVOFKVQ5dw@mail.gmail.com/
[2] https://lore.kernel.org/linux-fsdevel/[email protected]/